charles246

An explanation of how it has been "solved" would have been helpful to others. For people having this problem, make sure that you have "WideViewAspect=True: in your Fsg.cfg

I've never had this problem on other versions of FSX but since I have recently changed over to Windows 10, from Windows 7, I tend to blame the OS for this and not the Steam version of Fsx. What happens is that occasionally and seemingly at random, although probably more with PMDG products (video intensive?) the mouse cursor totally vanishes and pressing or moving the mouse produces a long series of beeps. I close FSX using the keyboard but the problem remains until I reboot the computer. I should mention that I play FSX in Nvidia Surround on three monitors. I have had mouse problems outside of Fsx since Windows 10 even though I think I have the correct drivers. I have also uninstalled all USB hubs from Device Manager and they were reinstalled after a bootup. This did not fix the mouse beeping problem which seems to occur only in Fsx. I welcome any suggestions. Thanks ​ Charles

Thank you! Yes that was the problem. I had forgotten that sometime ago I had installed a freeware weather program FSXWX and those two files, though not necessarily needed by the program , were included in the download.

When Fsx-Steam starts loading after the initial screen, I am now seeing on the top left side of the screen:"ENBSeries v0.075:GTA San Andreas boris-vorontsov.narod.ru". Can anybody tell me what this is. I don't recall installing any mods for Fsx or is this a part of the Steam atomatic update? Can I remove this? If so how. Fsx-Steam had never crashed on me before and has started to now. Thank you for any comments.​

It is hard to measure with any degree of accuracy a loss or gain of 3 fps between the two operating systems. I set my limit at 30 FPS. In Win7 as in Win 10 on Nv surround I get within .2 or so of the max with a default ac like the Cessna 172 in a default airport like Seattle. Definitely no change there. I now use Windows Borderless Screen with no discernible loss or gain in fps.I would suggest you temporarily disable Nv surround and run Fsx on a single screen, windowed. Run exactly the same scenarios later on surround.

If it helps you at all, this is my present setup: 4 monitors with three of the same resolution running Nvidia surround on my GTX 780 Windows 10 official release that I installed just a couple of days ago. As with Win 7, I can stretch the FSX screen in windowed mode over three screens nicely. No discernable loss of FPS from having FSX sized to one monitor on the surround screen. 4th monitor is enabled but only for non FSX screens. Two BIG differences however from my setup in Win 7 and my present Win 10 setup. In Win 7 : 1. I could drag an undocked window on to the 4th monitor that was not included in the surround mode and has lower resolution. Window would function normally and properly. However when I try and do that now in FSX on Win 10, the window I drag to my 4th screen would freeze and my other three monitors would be replaced by the contents of that window. Changing views would be taking place behind that large window but there is no way of seeing them. FSX seems to be still running but the only way to fix it would be to restart the simulator. 2. I used to use a program called pseudo Fullscreen, or something similar from http://ahkscript.org/ to make the surround screen full screen (slightly better FPS and realism) and still able to use the 4th monitor for maps etc. This doesn't seem to work with Win 10. I have the GeForce GTX version 353.62 But yes, it seems that NVidia Surround works reasonably well in Win 10 although it does still have issues with Fsx 2D screens, similar to Win7 but there are fixes for this. Hope this helps.​

Welcome. More on this here: http://www.fsdreamteam.com/forum/index.php?topic=11460.new;topicseen#new

SOLVED Found the answer myself. The problem lay in "fsx\Simobjects\misc". I had recently bought and installed Fsdreamteam GSX Ground services. These objects in the Misc folder were (And still are) causing the long Aircraft loading delay.

I hope that this is the right forum for me to post this puzzling event. If not, someone, please set me straight. I have relatively few aircraft in Fsx but most are payware and would have complex panels etc to load. It takes me around 17 seconds to get the list of ac once I hit the "aircraft" menu item within Fsx. This may not seem like an unreasonable amount of time, I know but it seems to me that it used to be a matter of 3 or 4 seconds earlier and I suspected a newly installed aircraft may be the reason for this delay. In an effort to decrease the loading time of aircraft and to discover which one was causing the longest load, I transferred all the aircraft within "fsx\Simobjects\Airplanes" to another folder called "hanger" in "fsx\simobjects", leaving only the default Cessna C172P. The result was that the delay was just as long. Any ideas as to why the delay is still there when there is a single aircraft in the folder? I will preempt any suggestions to defrag by saying that Fsx is in the root directory of my C drive, which is an SSD and does not need defragging. Thank you, Charles

I AM using the correct syntax and regarding the pressure on the system, it may be that I was multitasking at the time (can't remember) and another program might have upset Fs2Crew. My system is pretty powerful at 12 GB RAM and an i7-980 processor. Still, the frame rates, with the 737NGX are normally between 25-30, slightly less on the ground . The runaway with the speed occured at least twice and at the time I had absolutely no control on the speed settings even if I manually turned the dial. The only option was to disengage the AT but often too late to regain control of the plane. The Heading also went beserk, just once and kept going round and round after I gave a "set heading to xxx". But this only happened once and kept going even when I landed the aircraft and it was stationary. Thanks, I will certainly send you the log next time this occurs. I have flown several times since then, with no problem whatsoever. I appreciate the replies from all. Charles Macelli VATSIM 817692

I will remember that especially the "cancel last command" command which I had entirely forgotten. I wish though that there is a way to totally disengage Fs2Crew entirely from FSx, not merely muting the microphone (HM) in cases like this when the FO appears intoxicated.

I have recently updated to Fs2 Crew Voice version 1.5. I am not sure whether I had this issue previously but I don't remember. It may be something I am doing or not doing but this is definitely very odd. Everything is fine with the voice commands on the NGX737-800. However, several times now, when I am on the approach and give a speed command to lower the speed as in "set speed 150" with the A/T armed and SPEED set, the IAS/MACH indicator flactuates rapidly between 100 and top speed and often remaining at 340. If I manually try to reset it, it would go back to its highest setting or winds down to 100. At that point I would desperately unarm the AT and try and control the speed manually, often unsuccessfully for landing. Today the the HEADING command went crazy and and kept going round and round without stopping. With the update, I did reinstall the NGX SP1c. It may be other processes running in the background that is causing this anormality. However since this problem occurs mainly with the SPEED command, (today though the HEADING had a mind of its own as well) I am reluctant to blame this on other programs. At most times, Fs2 crew behaves nicely and I am very happy with it. However this latest problem is very frustrating. Does anyone know how to totally disable FS2Crew while flying the NGX if one needs to? I couldn't find it under processes in the Task manager. Thank You, Charles Macelli

Thanks for the suggestion . It was actually the A/T option that needed to be checked / unchecked (can't remember which) in the PMDG Setup menus.

Prior to installing SP1C and Fs2Crew (voice) I used to do all of this for takeoff and the NGX easily picked up speed for rotation at v1. After that the position of the joystick throttles didn't matter as throttle was controlled by the FMC. Now however I find that in order to reach V1 speed after I turn on TOGA, I need to continue increasing the joystick throttles (Cyborg X) further to almost 80% and speed still picks up slower. In flight I now have to monitor my joystic throttle position because if they are too high I overspeed and stall if they are too low. All this even though A/T is on and speed is supposedly being regulated by FMC. Is there a setting that I toggled inadvertently in the options? I am still learning Fs2crew but this behavior occurs even without activating the program.

Before I changed my C drive to an SSD, I had set my FSUIPC autosave every ten minutes (600 sec) and the delay during the save for the NGX was around 8 seconds and negligeable for other AC. I have now switched to an SSD, placed FSX in the root directory and run FSUIPC autosave every 300 secs (5 mins), leaving two saves. The actual save time is almost instant as compare to the 8 seconds with a normal SATA drive. Each save consists of 3 files. In order to avoid a saturation of files in the PMDG /Panelstate folder which may crash FSX and will also show in the FMC, I followed the advice here: http://forum.simflig...d-the-pmdg-ngx/ and added 3 lines in the FSUIPC.ini Hope this helps others.

PROBLEM SOLVED Thank you all especially to those who pointed to FSUIPC autosave feature. That definitely was the culprit. He had it activated on the ground, every 30 seconds. We then set it for two minutes and almost exactly to the second, everything froze for a few seconds. I imagine that since there is more to save with an AC like NGX, the save is very noticeable but will not be as much or even discernible in other aircraft. Thanks once again now my problem is whether to buy this for myself before SP1 comes out; right after SP1 or wait for other bugs to be ironed out.

I will begin by saying that I personally still do not have this amazing product. From what I have seen and read, this aircraft beats even my own favorite, the JS41 which I did buy just over a year ago and which I use with religious awe very frequently. Both myself and a friend of mine had some time ago decided to purchase the NGX; I opted for waiting for SP1 whereas he went ahead and bought his. He is somewhat disappointed (to put it mildly) but I will hasten to say that this is not a reflection of the product but I suspect of his equipment. Since his specs are almost identical to mine, I will wait until he solves his problem before purchasing my copy. The Equipment: Alienware, Aurora ALX I7-x980 (12 Core) @ 3.33Mhz; Ram: 12 GB. GeForce GTX 480 w/ 1.5 MB RAM; Secondary Geforce 9800 (not used by Fsx); Windows 7 Home Premium. FsX Delux w/ Sp1 & SP2 installed in default C:/microsoft games. The Situation: NGX loads fine; looks great and frame rates are decent (>18). Aircraft is Cold and Dark, loaded AFTER the default Cessna being cold and dark situation. The problem: Even while panning around this wonderful cockpit, there is a regular 8 seconds pause after every 30 seconds. In five minutes I counted 5 or 6 short freezeups of approximately 7- 8 seconds duration. Apparently the lag was worse before I deleted his FSX.cfg and started a new one. His sliders are set to mainly high with little or no land, sea or airport traffic. This frequent lag ( 48 seconds every 5 mins) obviously make this AC unflyable for him until he finds the cause. He also has PMDG's JS4100,and this also gets a decent 18fps> on the ground in a major airport and has no stutterings (is that what this is called?) with his previous CFG or with the clean one. I realize that the NDG is probably more intensive but you can't argue with his equipment. In any case, lowering all settings to low didn't make a difference to the problem although an obvious inclrease of fps. May I say that he doesn't run any add ons whatsoever; have very few if any non-default AC and is not connected to Vatsim when this is happening. The attempts for a solution Disabled every other process running on the computer that wasn't essential to the system, including antivirus (AVG) Replaced FSX.cfg with a new one. Set Priority to High in Task Manager for Fsx AA Off / On didn't matter Hard Drive, cleaned and defragged Nothing runs in the background (that I can see) Prayer.......(no help there either!) I realize that there are myriads of other possible experiments one could try, including Nick's, wonderful paper but the fact remains that only the NGX does this to him. Since I have the same processor (but less RAM) I think I will wait this one out for a while until a solution is found. I found the I7-x980 Processor (very expensive) a little quirky with some games (I am not by any means equating FSx with a "game"). For example it doesn't run "Saboteur" or "RelicCOH", probably because of multithreading so I am inclined to blame it at this point. However, this could be a simple problem. I suspect that this is a unique problem because although I have done an extensive search of this forum, I came up with no mention of similar occurences. I'd love to buy the product myself but I suppose I will have to be content with flying the Jetstream a little while longer. If anyone has any solutions or suggestions to this, I would be certainly appreciate them. Thank you in advance. Charles Macelli

Sometimes, a simple solution is often ignored. Did you try renaming (or deleting) your Fsx.cfg yet? It is the first thing I do whenever I have any problems with Fsx. You would start with a newly created Fsx.cfg and if the problem persists, then you can rename your old Fsx.cfg file back and try other options.

OK... good to know..

Am I missing something? When I bought the PMDG J41 in January of this year, the Weather Radar system was not being simulated ... only the two switches on the right side which control the radar range of your flight plan were/are functional. The Operating Manual on Page 55 states that "NOTE: In this simulation, all items in italics are NOT being simulated. They are included for informational purposes only." The only part NOT in italics is the RANGE. Nice as the JS41 is, a non-functioning weather Radar is, for me, quite useless which is why I replaced it with the GPS500 which now has more functionality than its pop-up counterpart and does not need to rely on the programmed FMS flight. In fact I can now load MSFdefault flight plans and the NAV will follow these.Is there a more recent version of the JS41 that I am not aware of?Thanks for this.

It ultimately depends on how much you want / can spend on a new system. The default AC, with most sliders set half way, FSX would give you a good performance on on a Quad or Duo core processor with 4 GB RAM on a 64Bit OS. This is what I had last year with my Dell XPS720 Quad 6600 processor and 6 GB RAM. On this machine and on the ground at a large airport with very careful use of the graphic sliders, I was still only getting about 12 FPS with the JS41 but triple that on the default AC.A few weeks ago I got an Alienware Aurora ALX from Dell,spent over a grand more than the advertised price to up the Processor to a factory overclocked I7-980X and the Graphics card to a GTX480 and the default 12 GB RAM. I probably could have spent less money but I did want to see what I can get out of my favorite AC, JS41. All sliders are at or close to their max (with the exception of road traffic...useless huge hit on FPS) and at the same airport and on the ground, I now get twice as much FPS on the JS41 (23-25 fps) and considerably more on the default AC (w/ High and Ultra High settings). I'm afraid, that's the price to pay for PMDG's awesome products. Bottom line is that you would be quite satisfied with FSX on a system that had even 6 GB RAM and an I7-920 (at least) processor running on a 64 bit system.

For anyone interested, I did manage after many trial and errors, to fit in the default Fs GPS500 in the nonoperational WX panel. It is fully operational (unlike the popup GPS) and may be used instead of the default FMS..........................................................................Make a copy of the default PANEL.CFG first................................................../ VC SECTION 2///////////////////////////////////////////////////////[VCockpit02]size_mm=1024,1024pixel_size=1024,1024texture=$GaugeTwobackground_color=0,0,0gauge00=j41!pmdg_j41_rmu_1, 0, 0, 393, 500gauge01=j41!pmdg_j41_rmu_2, 393, 0, 393, 500gauge02=PMDG_BAe_JS4100_3!GNSXLS, 1, 508, 512, 408gauge03=j41!pmdg_j41_alt_pic, 896,0,128,508gauge04=fs9gps!gps_500, 500,480,526,378gauge05=j41!pmdg_j41fms_pu_open, 919,458,53,35.................................................................Only the gauge04 line was added................