antonvs

Thanks for the memory Michael. I wonder how relevant this page will be: https://www.flightsimbooks.com/flightsimhandbook/keyboardcontrols.php Just to clarify for newcomers, this book covered the old MS Flight Simulator ver 5.0 (from the mid 90’s)

Thanks for your kind comments Dave. I guess regardless of the theory involved, the worrying issue is that even though the current release of FSc in 64bit is fairly light on scenery, systems and only two aircraft I and others have noted frame rates dropping to low 20's and staggering at times. It raises the question for me what happens when the new full sim is loaded to the same extent that we currently have with either FSX or P3D. Just wondering I guess. By the same token I'm quietly confident (and hopeful) that as time goes on, DTG will refine their coding.

Now that I have spent a few hours progressing through the LAPL, here is a list of features that I would like to see concidered for Flight School to make the learning experience better. I have avoided making suggestions regarding scenery as I don't see this as a core issue. - Radio Tuning, allow fast tuning by MHz units as well as just the existing KHz units - GPS built into VC panel in Arrow - heading bug needs to display degrees so it can be set accurately. - joystick button configuration in settings. - quick guide to keyboard commands and instructions like where is the flap lever. If this school is targeted to new comers, I'm sure these are the type of things they will need to know. Or at least be able to ask the instructor. Maybe when the instructor says "flaps" and nothing happens he can point to the handle or say "or press F7" What do I think of the Product. I'm loving it, for a first release I say well done Dovetail. Moving through the training levels and the user interface is fun. I thank you. Mods - accidentally double posted. Please delete

Now that I have spent a few hours progressing through the LAPL, here is a list of features that I would like to see concidered for Flight School to make the learning experience better. I have avoided making suggestions regarding scenery as I don't see this as a core issue. - Radio Tuning, allow fast tuning by MHz units as well as just the existing KHz units - GPS built into VC panel in Arrow - heading bug needs to display degrees so it can be set accurately. - joystick button configuration in settings. - quick guide to keyboard commands and instructions like where is the flap lever. If this school is targeted to new comers, I'm sure these are the type of things they will need to know. Or at least be able to ask the instructor. Maybe when the instructor says "flaps" and nothing happens he can point to the handle or say "or press F7" What do I think of the Product. I'm loving it, for a first release I say well done Dovetail. Moving through the training levels and the user interface is fun. I thank you.

I take your point Paraffin and I don't knock the capability, I guess the point I'm trying to make is that I have really stretched on a retired budget to get a $3000+ system and its the practical limits of 2-4Gb video cards or 16-32Gb of ram that I hope a free for all product development could soon fill up. And with the physical limits you correctly mention and the cost per Gb we would soon be looking at a system cost of $30k onwards.

Good ideas and questions J. but spending 64bit space is probably like spending money, it soon goes. So I hope DTG put the brakes on and concider system usage very carefully least we be soon back in a similar position to how we have been with FSX in a 32bit system.

Don't know where I have been but what do all these terms mean, are the specific to P3D or to do with CPUs and Motherboards. I would love a quick explanation please.

So hear is the good news! All is well. Here are the two things I did that solved the problem, I offer this in case it helps anyone else. 1. Ran Steam "Verify integrity of installed files" from the Steam client under properties of FSX This found 4181 files that failed the integrity test. 2. Reinstalled the latest version (4.949h) of FSUIPC4 These two things done cleared the CTD's and all other issues. I was then able to reinstall all the files that I had removed and now back to flying with colors. Thanks again Jim for your help. And hope it helps someone else.

Hi Jim and thanks for coming on board. The three files I replaced were recent backup (prior to this current mishap) from the live install and that process worked ok, but did not solve the problem, just proved that fsx:se is ok. I will try installing the latest version of FSUIPC4 but the version I have (probably 4.9.1) was running fine and I have a gut feeling it is something in FSX:SE that is corrupt. Just hesitant to run a repair at this stage as I mentioned, it runs so well otherwise. Anyway one step at a time.

A progress report. I can confirm that my original error was to inadvertently use Flight1 GTN config tool on the wrong plane. I had tried adding a second gtn750 to the Flysimware Learjet 35A (GNS) version instead of the (GTN) version (in a senior moment). So far to try and get my system back to normal I have done the following: 1. Updated drivers via Driver Blaster 2. Tried replacing FSX.EXE, g2d.dll and g3d.dll from a backup 3. UN-installed the GTN 750 gauges 4. Un-installed FSUIPC4 and reinstalled 5. Un-installed Flysimware Learjet 35A Rebooted, but with all the original problem add-ons removed FSUIPC4 is still reported by FSX:SE as having a problem in module FSUIPC4.dll Flight1 via the Simconnect forum say it's not their problem. I'm yet to hear back from FWS so my options are thinning. I'm hoping I don't have to face a full rebuild as the Sim will run ok with any aircraft (Inc add-ons) as long as I don't load a GTN version and the Sim runs very well, even for long periods and will shut down ok and save the flight to the logbook. But with the cavert is that I can't use FSUIPC4. The last rebuild I did took a month or so to complete so I naturally hope to avoid this option. Any help please would be very appreciated.

Hi, I wonder if some of the guru's in this community could help me analyse the attached minidump error files in the hope of tracking down a problem that has arisen whereby FSX:SE now crashes on exit (CTD) after any flight with the exception of a short hop in the default Trike. Links to minidump error reports. Two dumps happened during the CTD process. 1st http://www.evernote.com/l/AE32OKe8d6FLzaLk06Kmy4UPXDdMLtJH2EE/ 2nd 30 sec later http://www.evernote.com/l/AE1SPAthkXNDvLoZX_Is0mnkd9aEPLsGYm4/ Background: FSX:SE, Win10, i7 64bit, 16Gb RAM PC, DX10, Steve's fixer, ASN, FTX GLOBAL, Pilot's FSGlobal 2014 mesh. I have had my GTN750 gauge running successfully for a few weeks. Then Successfully installed into my Flysimware Learjet 35A. Not content, I then tried to install a 2nd 750 into the same plane using your installer. Result. FSX CTD on first load. 2nd try I got an err msg "FSUIPC not supported". I answered "yes" to continue anyway. FSX then failed to load. On a 3rd try, I said "No" to FSUIPC and FSX ran after I selected "yes" in controllers for Joystick. The LJ35A ran ok with a single 750 gauge. In addition to having no use of FSUIPC I also find that any flight (even a short taxi) results in FSX CTD on exit (every time). If I Start FSX and select aircraft, location etc. but don't start a flight, I can exit ok without a CTD. This happens when loading my RA Legacy V2 as well. I have yet to try a reinstall of either the GTN750 or FSUIPC. I have checked my Logbook.bin file and it appears to be ok as it reads in LogEdit. I have also run FSX without loading ASN (but I have not reinstalled ASN) Any help or suggestions would be greatly appreciated.

I used Windows uninstall (which is an option given by FSW). I did leave the folder which had three Addon repaints which I edited back into the new "aircraft.cfg" file. I'm also using the Freeware weather radar and also made the necessary changes to "panel.cfg"

I too downloaded and installed ver 2.2.6 after uninstalling 2.1. But my experience is not very good so far. 1. Attempting ALTSEL on climb or decent fails for me exactly the same way as ver 2.1. I set a target altitude and select ALTSEL, when the altitude is close a notification sounds (correctly) and the ALTHOLD light comes on but the plane continues to either climb or decend. I found if when the ALTSEL light changes to ALTHOLD I manually click off ALTHOLD and then back on again, the plane will then hold Altitude. But tgus is only a workaround. 2. I also found that it is no longer possible to store a Direct To waypoint on the GPS (GNS). All works well until pressing the Enter button to store the waypoint. Pressing the key has no affect. 3. Then I found that I could not get the Autopilot to follow a flight plan. Not sure of the exact details, just didn't work as nirmal Has anyone else experienced the same problem?

I note I have got ver 2.1 and can confirm that I too have a problem capturing ALTSEL, either in climb or descent. I run in FSX:SE with W10 on an i7 4770K PC with a GTX770 2Gb vid card. After a few hand flown flights I really enjoy flying this plane. I will longingly wait for the next update to see what the plane can really do.