Hi Ian,

Flight.exe doesn't like the /3GB switch on the command line. Is there some other way I should be applying this switch, or have they removed it from the final release?

Use 4gb_ patch.zip to modify flight.exe ...Happy FSX FlyingsPierre LFBE

Maybe this will help.... < There, two .jpg files almost unreadable >

Hi Alain,Just for reminder, why don't use the "code" facilities to insert text in your message, it's much more readable ?Happy FSX FlyingsPierre LFBE

Edited March 2, 201214 yr by Papy_Pegase

Flight.exe doesn't like the /3GB switch on the command line. Is there some other way I should be applying this switch, or have they removed it from the final release?

This worked for me (Vista 32bit):HOW TO PROPERLY TUNE VIRTUAL ADDRESS SPACE IN WINDOWS (x32) FOR OUT OF MEMORY ERRORSFor Vista:1. Open a command prompt with Administration rights. You find the command prompt box under "Programs-Accessories-Command prompt" 2. Right Click the command prompt and select "run as administrator". 3. Enter in the box at the prompt: (copy/paste if you wish) bcdedit /set IncreaseUserVA 2560 and press enter 4. Reboot TO set that back to default in VISTA just start the command line prompt with Admin right again and type: bcdedit /set IncreaseUserVA 2048 Hit enter and reboot

@ IanMore specifically, abstract from : Simviation Forum › Current Flight Simulator Series › Flight Simulator X › XP/Windows Setup, System Optimizing and Drivers

USING MORE/LESS or EQUAL to 2GIGS OF SYSTEM MEMORY IN WINDOWS XP x32 OR VISTA X32 with OOM-OR-HOW TO PROPERLY TUNE VIRTUAL ADDRESS SPACE IN WINDOWS (x32) FOR OUT OF MEMORY ERRORSx64 operating systems do not need the following changesThis change only tweaks the address space, relieving the OOM error. The 32bit system will use the physical memory installed up to 4GB regardless!If you have XP or VISTA x32 and more than 2GB you need to MARK the OS for that use or it will ignore the sticks and never use themx64 operating systems do not need the following changesFor XP:disable hidden files and folder, then on the root C: you will find a file named: boot.iniOpen it in notepad and add the follwoing to the end of the OS boot line:/3GB/Userva=2560multi(0)disk(0)rdisk(0)partition(2)WINNT="Microsoft Windows XP Professsional" /fastdetect /3GB /Userva=2560 <---- add it heresave and close the filerebootto set that back to default, simply remove the editIf you are using XP SP2 and are running a dual, quad, OR a single core Intel HYPERTHREAD processor, make sure this update is applied :http://www.microsoft.com/downloads/details.aspx?familyid=C2AB5A48-8240-4934-BBD8...Systems running XP-SP3 does NOT need that updateFor Vista:WINDOWS VISTA ONLY: 1. Open a command prompt with Administration rights. You find the command prompt box under "Programs-Accessories-Command prompt"  2. Right Click the command prompt and select "run as administrator". 3. Enter in the box at the prompt: (copy/paste if you wish)bcdedit /set IncreaseUserVA 2560  and press enter 4. Reboot TO set that back to default in VISTA just start the command line prompt with Admin right again and type: bcdedit /set IncreaseUserVA 2048 Hit enter and reboot Make sure you have the VISTA updates from Windows Update installed that address out of memory errors too.http://www.simviation.com/cgi-bin/yabb2/YaBB.pl?num=1188591122As long as you have Vista up to date with Windows update... or SP1 for Vista installed, you should already have those patches

Pierre LFBE

This worked for me (Vista 32bit):HOW TO PROPERLY TUNE VIRTUAL ADDRESS SPACE IN WINDOWS (x32) FOR OUT OF MEMORY ERRORS

Does anyone know how to do that for Windows 64?

Does anyone know how to do that for Windows 64?

For 64 bits Operating Systems (WXP x64 or Windows7 64) it's useless, these OS have access to the whole memory addresses.Pierre LFBE

UserVA=2560 will not do it for Flight! Works great for FSX, though!You have to leave out the UserVA= setting to get the full 3GB (with some risk that other programswill misbehave..)This is for Win XP SP3.

Edited March 2, 201214 yr by Bert Pieke

Micro Stutters in Multiplayer ![Q] getting micro-stutters in multiplayer for a brief second whenever someone enters or exits the session ?[A] this is a known issue related to SimObject loading. It is probably worse when the other player has an aircraftlivery that isn't already loaded.Fred

Latest News from the Dev team !..........about the REWARD for reaching level 20 !" The XP Grinder Achievement isn't currently working. We're aware of the issue and it will be fixed in our next update. The fix will be retroactive, so if you've earned the necessary XP, you'll get the achievement. "They have asked us beta testers to spread the word.Fred.

Edited March 3, 201214 yr by RYR738

Keep in mind that the flight.exe is already LargeAddress Aware, so there's no need to "patch" flight.exe like we did with fsx.exe...

Folks with high end systems might find this helpful !Latest from the Dev team !" We have found Flight tends to be CPU bound on higher end systems, and GPU bound on lower end systems so I am not surprised by your results garsands. On higher end systems this usually manifests as the primary core being at 100% while the other cores may not be. We did a lot of work to improve the threading in Flight, but the D3D api has a reliance on the primary core, so the rendering all has to occur on that core. D3D11 offers the ability to do some work on other cores, but there is still a core set of operations that must occur on the primary one. In D3D9 everything is on the primary core. "Fred.

Folks with high end systems might find this helpful !Latest from the Dev team !" We have found Flight tends to be CPU bound on higher end systems, and GPU bound on lower end systems so I am not surprised by your results garsands. On higher end systems this usually manifests as the primary core being at 100% while the other cores may not be. We did a lot of work to improve the threading in Flight, but the D3D api has a reliance on the primary core, so the rendering all has to occur on that core. D3D11 offers the ability to do some work on other cores, but there is still a core set of operations that must occur on the primary one. In D3D9 everything is on the primary core. "Fred.

Thanks for passing the information along.Also let me say it was nice of the MS team to lift the NDA and let the beta testers double as little volunteer MS PR reps in a way. :) A lot (most) of developers don't lift NDAs.

the beta testers double as little volunteer MS PR reps in a way.

:LMAO:What a joke...I only "call 'em as I see 'em""little volunteer MS PR reps"

I didn't mean that in a bad way at all. Most beta testers are willingly to help and give to the community they are involved by passing along critical information that the others outside the veiled curtain of testing could use.. Like I said though, most developers never lift NDAs or even ease up on a term in them.. Heck, I've been tied to one for over a year and a half. It was actually a ballsy move for MS to lift the NDA after release.

About the graphics settings in the update !

 

" The main change to graphics settings in this update is that on Maximum settings the culling radius of the autogen was reduced from 10 pixels to 5 pixels which should increase the draw distance of smaller trees and buildings. This will also have a slightly negative impact on framerates. I don't believe anything else was changed other than fixing Custom=1 so that it worked as intended. "

 

Fred.

I think it is very important before you start to fly to make sure you go into Options/Aircraft Controls and select Invert Mouse Pitch.

If you don't you will start learning a very bad habit......and it's very hard to undo later.

 

This is the first thing I noticed when I downloaded the game a few weeks ago and went searching for this option.

 

VERY GOOD ADVICE