uuu100145j

Sorry for the 7-year-old reply, but yes it solves the graphics issues and stuff (I had missing textures (default ones!) and changing it to one worked)

That is if you want to use the default aircraft. If not, it probably is the AT-502 (but the P-51 is way faster than the AT-502, the AT can only fly at 400 km/h while the P-51 can manage 700 km/h)

Actually I think the default P-51 Mustang CAN be used. Dusty IS in fact a P-51 Mustang and a simple repaint (with those eyes) can help.

Did you do manual install?

Exactly what i'm doing now.

I found out a fix (no test flight, but it should work) Connect Controller using FSUIPC instead of using FSX. Video here (its expensive but worth it) https://www.youtube.com/watch?v=hRGPNVtf2Cw

If you want solid joystick performance, don't install FSXAssist. It sometimes will still fail, like my Singapore-Brussels test flight. Only option: Windows 10 Technical Preview. (Which I will not care about those complicated stuff)

Good, you use the same joystick as me (more relevant). However, I don't use 2 monitors (probably does not matter) First, delete those registry files as I said on page 54 Then, buy FSXAssist (no other way, but if it works, its worth it) It worked for me! Alternatively, you can use Windows 10 Technical Preview (a complicated process where you have to backup your Windows disc etc.). dmiannay has tested it out, and it worked for him (see pages 53 to 56) If you use FSXAssist, make sure to restart FSX after EVERY flight. If not, FSXAssist would not work for the subsequent flights. Hope this works! I'm doing another test flight (2 flights in a row! Dubai-Singapore-Brussels). See if FSXAssist works. If it does, success! I tried doing it once but I aborted takeoff (joystick fails at 110 knots) UPDATE: knew it wouldn't work. Restarting FSX...

No disconnects! (even though I reset the flight thrice) Seems to disconnect very randomly. (maybe the EnumerationRetryCount value did matter after all...)

Maybe not, I was wondering if the Joystick Disconnect after Parking (normally after 1 hour) would count... It does disconnect if I start a new flight (np for me, I could just restart FSX) Thought of doing one last test flight (Same flight, but clicked "reset" once) P.S If FSXAssist shows 'FSX is Restarting', then is FSXAssist connected to FSX?

Well, It happened again. I'm afraid I have to call that 30 day policy into place if it happens again. (This time round I did not reset the flight or change aircraft...) Next test will be from Cape Town the Dubai (9 hours) Time for Windows 10 TP (another $30 gone, thanks to microsoft trying to wipe out everything in my current drive if I use it)

Finally, FSXAssist started to not work for once. The "controller engaged" button does not mean anything, and the controller is gone during taxi to the gate. For the first time. Don't know if it is gonna get worse (I did not reset flight, and this is the first flight) Changing aircraft will cause this problem, as well as changing scenery settings, etc. If that loading screen comes up (not the blue one), will FSXAssist still work? I'm losing patience, I'm gonna use Windows 10 TP for the sake of FSX. How do I reinstall Windows 8 afterwards (not gonna buy another hard disk for $50 for the sake of this). They said Warning Creating a recovery drive will erase anything already stored on your USB flash drive. Use an empty USB flash drive or make sure to transfer any important data from your USB flash drive to another storage device before using it to create a USB recovery drive. And do I need to reinstall FSX if I go back to Windows 8?

Thanks! FYI I did not notice any problems with the blurry ground textures though, and I finally made my first smooth landing since I used windows 8 (-89fpm) Thank you to the team at SkyPilot! Anyways, how do I use the "App path"? I'm confused with the documents saying "exe.xml" files. Most of the addons are either scenery (.bgl) or .dll, not .exe or .xml

I experience problems when using FSXAssist When it is ran, the FS sounds have a lot of static. Yes, it is comforting that I know that FSXAssist is doing its job, but the static is also very annoying.

For FSXAssist, I think it only works for the first flight (it disconnects if I don't restart FSX and FSXAssist) And for the subsequent flights, the "Controller Engaged" text does not do anything. Anyways, another satisfied customer (for now) I'll do it if joystick disconnects again (hopefully not!)