IFly- yeah, this is why I suggested you wait a bit before you get one of these ArteryTek aio’s. I’ll have to give it a good inspection after flashing the esc’s. It’s hard to say at this point if that was esc based, especially since it was having issues getting enough power to the motors, or if I bent a shaft during one of the times where it decided to not create enough thrust to keep me in the air and slammed into my deck, roof, or trees. If that doesn’t show promise, then I’ll swap the aio tonight.ĭuring my short flights between crashes on Monday evening, I was get some “throbbles” (shakes/wobbles on quick hard throttle punches), especially when trying to power out of a drop. I’m going to try dropping that hf32 firmware on the esc’s tonight. I should have done that initially, but, excitement to try a bunch of new things got in the way of logic and best practice. Pathfinder- excellent advice and definitely what would be a less frustrating way of doing things. When you have mastered WS and the AT boards on separate platforms, then you can think about combining them and hopefully by then i will also have WS and you can give me the lowdown. Trying to run something new to you, on a board that is also new to you, is kind of unwise. Then they will hack something together from swapping WS to a more mainstream is probably wise. That will probably come when BF releases a stable target, so probably when 4.5.1 or similar is released. But I'm also waiting for a QS compatible build. If I can get it to fly, I will consider it a success. I will be ordering one in a couple of months. It will take a while for them to get mainstream and stable. You never install updates until a month or so after they come out and even then install them on test machines first to avoid mishaps. NET 3.5 issue.(1, 09:30 PM)iFly4rotors Wrote: Think I will wait until they get all the "kinks" worked out. So I think it's entirely fair to say that this is another case of the Alder Lake issue and not the comparatively much rarer. Every computer with an Alder Lake processor has this exact issue and this exact error code.The error code for the TS3.exe errors is the well-known divide-by-zero code that is pathognomonic for the Alder Lake issue.The OP's dxdiag shows that the faulting module is TS3.exe, not Sims3Launcher.exe, so the process is getting past the launcher and therefore also getting past the point where.This happens before the launcher opens.When you first launch Sims 3, Windows will ask to install.NET Framework 3.5 isn't pre-installed in Windows. NET FRAMEWORK 3.5 NEEDS TO BE ENABLED THE FIRST TIME IT IS CALLED BY THE OS!!! IT DOES NOT AUTOMATICALLY GET INSTALLED!!! NET FRAMEWORK 3.5 FOR THE LAUNCHER TO RUN!!! ON A FRESH INSTALL OF WINDOWS 10. Any and all advice is appreciated more than I can THE SIMS 3 REQUIRES. I have absolutely positive that this is an easy fix that is right in front of me and that I'm just not getting, so apologies in advance. I ran a DxDiag using the instructions here and have attached it to this post.įull disclosure: I am awful with computers.zip and launch the patcher." They mention that by the "patcher" they mean "AlderLakePatch.exe," but the only remotely similar thing I can find on my end is "," and I haven't been able to do anything with it. I have been trying the AlderLakePatch, but can't figure out how to "extract the. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |