Archived

This topic is now archived and is closed to further replies.

Ultor

FSLabs Concorde X - still OOM plane?

Recommended Posts

I heard three years ago when this plane was released, there was an out of memory bug quite often present. However since that time two service packs were released so I wonder if Concorde-X's memory management within FSX improved now? 

Share this post


Link to post
Share on other sites

You definitely need to adjust your FSX settings to accommodate this add-on with any machine. It's funny because I never used to get OOM with the ConcordeX, even when I used to run an high settings. But now I simply can't.

Share this post


Link to post
Share on other sites

All settings maxed out except traffic, never had OOM. I have:

 

- microsoft fix applied http://support.microsoft.com/kb/947246

 

- Texture max load limited in fsx.CFG to 2048

 

-all payware scenery disabled in scenery library. I use sceneryconfigeditor to enable only scenery which i need for next flight, every time before i start FSX  https://www.dropbox.com/s/mikr1t69emo781i/SceneryConfigEditor-installer-1.1.1.exe

Share this post


Link to post
Share on other sites

I actually done some VAS testing the other day and found that having FSDT KJFK V2 on only added 100 onto the VAS whereas UTX added about 500. Do you have UTX and do you disable that also?

Share this post


Link to post
Share on other sites

I am especially worried because I still use 32-bit Windows version for some other reasons with 4 GB of RAM. That's why I am not sure if Concorde X will run on my rig at all. Anyway thanks for your input. In the airliners area I consider three products to be able to fully diverse my flying experience: FSLabs Concorde X, A2A Boeing 377 and jet from pre-FMS era like Coolsky DC-9-30 or MilWiz Boeing 737-200.

Share this post


Link to post
Share on other sites

Nah, 'oom plane' sounds a bit harsh. She's indeed very demanding on the memory, perhaps due to the tons of 2D windows (being necessary). Same as for some of you, I have to watch my settings to allow for the coexistence of that beautiful Concorde and some nice scenery. Means, yes, I had ooms from time to time. For example, Orbx Brisbane comes to my mind. :blush:

 

I could be totally wrong but I don't think the service packs addressed oom issues. If I understood the devs correctly, there isn't much you can do with the plane when it comes to keeping the level of optical detail, clickspots and the mentioned 2D panels. Optimizing would mean cutting right through her.

 

If one would be constantly haunted by ooms, perhaps a manual edit of 2D windows (backup first, especially the panel.cfg) would allow for dropping the ones which aren't needed for your flying style. But that's a huge guess of mine. I'm on standard config, normal texture size and rather low-ish FSX settings when e.g. flying to Aerosoft's Anchorage or the New York area or SFO.

 

In my lineup, the only planes being somehow sensible to memory related exhaustion are the Concorde X and NGX. So you gotta watch every 'X' as it seems. :lol:

 

On the more scientific side, the tip from Zeljko is a very good one. Don't enable too much scenery. Only the parts you are flying to, perhaps some favourite alternates in between. FSX does seem to collect a lot of memory items enroute, so the dreaded oom scenario may then take place when you have the most fun, at the landing. :mellow:

Share this post


Link to post
Share on other sites

OK, but why dozens of 2D panels are needed in Concorde X? Is its VC cockpit so inaccurate or non-operational it is impossible to operate switches, gauges etc.directly in VC?

Share this post


Link to post
Share on other sites

The VC engineer panel is just a mock up, and you have to use 2d panels to operate it. Other than that, VC is fully functional. Unfortunately, if they made full working VC engineer panel, that would kill fps - simply too much gauges and switches.

Share this post


Link to post
Share on other sites
Is its VC cockpit so inaccurate or non-operational it is impossible to operate switches, gauges etc.directly in VC?

You are right, the way I wrote it, one could think that.  :blush:  So I have to add how she works in terms of the 2D usage. You have the full 'front' VC with additional windows available for popups or in case you would want to fly with only the 2D cockpit. So that's like on some other planes too. Fully featured setup.

 

But the engineering panel is the one causing a lot of work on 2D panels as the VC representation is more or less static and when you e.g. click the spot for the overwhelming fuel panel, that one pops up in full detail. Same for the other various panels, referring to their systems. It's all simulated, so there really is a lot.

 

If I got them (the devs) right, they couldn't model the engineering panel in the 3D VC as the normal 'front' VC already is that detailed. Tons of analogue gauges and knobs, all working and being clickable. So you have some windows you can avoid when using the VC only, but you have others (engineering) which can't be avoided unless you are using the automated flight engineer to e.g. work on the pressurization and fuel for you. That's what I meant with 'in regard to your flying style'. The ones working the Concorde on their own can't leave out that many 2D panels. And each opening of such sub panels adds to the memory load of FSX.

 

Edited. g_precentralis was quicker. :smile:

Share this post


Link to post
Share on other sites

OK, so assuming I fly in VC with help of virtual flight engineer there is no necessity to pop-up so many 2D panels which crash FSX memory management?

Share this post


Link to post
Share on other sites

Yes, we may assume that. If you would really stay away from using e.g. the fuel panel, you would save the memory impact. But lets not forget what others and I reported. Which is, you can fly her in full without any oom if you keep an eye on your settings and the active scenery.

 

/ sent from a mobile device tracking my whole life for no reason /

 

 

Share this post


Link to post
Share on other sites

Well, buying Concorde X is a bit risky move from "OOM standpoint"... :wacko:

Share this post


Link to post
Share on other sites

Then switch to the Concorde viewpoint immediately. :D Seriously, I can understand your concerns. I think Aerosoft sells a box version, maybe they offer refunds too. I have the pure FSL download.

 

/ sent from a mobile device tracking my whole life for no reason /

 

 

Share this post


Link to post
Share on other sites

Well, I am afraid I am at my wits end with the FSL Concorde-X for the moment. I have never had a OOM before but now it is all I have ;)

 

I wanted to find the culprit so I used SceneryConfig Editor and removed all but the default scenery.

 

I read the support thread over at FSL from the start and followed every advice, installed the newest C++ redist as per the support article regarding Acceleration.

 

I pulled down my details and autogen lower than I ever had them. AI / vehicles / boats are (always) at 0. LOD is at 4.5, textures at 2048. I have Ezdok and FSUIPC active on the main FSX PC.

 

I normally run WX, SB4, EFB and BAV's ACARS networked on a laptop but nothing was connected for this test today.

 

On the "Fly Now" page with the trike situation stable, memory for FSX is 650Mb, when I select the Concord it goes to 1215Mb, I load the situation file for the tutorial and let it stabilize, I end up at 2338Mb, I apply groundpower and load fuel and takeoff card, I am at 2762Mb, still following the tutorial, I am pushing back at 3028Mb and FSUIPC starts to chime. As I am taxiing to 27L some textures outside, and in the cockpit, goes black and I am at 3265Mb, and finally, on the takeoff roll I OOM'ed.

 

So, for now I am parked, I hope someone can point me to a place to start the troubleshooting:

 

Is my startup load abnormal? 650Mb when stable at Free flight page?

 

Are there typical fsx.cfg setting I could have acquired that would cause this with the Concorde, but not with NGX, MD-11, J41 or RealAir Duke (wich are the only addon aircraft I have ever installed).

 

Where can I find the non-default "dll"'s that are loaded with my FSX? I am thinking to backup my fsx.cfg and let it rebuild, applying the highmemfix and wideview only, and see what this does to my default startup VAS.

 

Interesting also to see if the inherent VAS accumulation with Concorde will decrease with a clean / different cfg.

 

Thanks guys,

Share this post


Link to post
Share on other sites

mosteen, how do you check VAS usage?

 

I am now in the air in PMDG MD11. This is typical for my flights in task manager:

 

 

And this is FSX only in process explorer:

 

 

 

Share this post


Link to post
Share on other sites

I'd go for the reduced textures when installing her. The installer asks for the type of textures and if you avoid the 2048 ones, you should already be able to reduce the impact. Sooner or later you may use the external view, so that's where the impact happens regarding those textures.

 

As for the dlls (namely the ones which may not be needed when running just Concorde), head to C:\Users\Morten\AppData\Roaming\Microsoft\FSX and backup your current dll.xml. After that, you can edit it with a text editor and get rid of (for example) PMDG dlls, the one from RXP, perhaps those from Orbx and so on. They don't cause harm by design, but if they don't get loaded, they can't cause harm.

 

You are starting at London, right? Do you have any extra scenery installed which makes use of the default scenery folders? I recall people running into trouble (regarding oom) with certain freeware for power lines and things.

Share this post


Link to post
Share on other sites

 

 

Don't enable too much scenery. Only the parts you are flying to, perhaps some favourite alternates in between. FSX does seem to collect a lot of memory items enroute, so the dreaded oom scenario may then take place when you have the most fun, at the landing.

 

That is one aspect of FSX that totally baffles me. Why would you create a piece of software that loads stuff into memory that you may never actually see on your flight? I mean, I can understand loading stuff in advance within a certain range of the heading that you are flying, but FSX seems to load just about everything this side of the galactic centre! Surely that's crazy?

Share this post


Link to post
Share on other sites

Then switch to the Concorde viewpoint immediately. :D Seriously, I can understand your concerns. I think Aerosoft sells a box version, maybe they offer refunds too.

 

Unfortunately Aerosoft can grant you money back but only if purchased DVD box in unsealed which is pointless in this situation.

 

 

I'd go for the reduced textures when installing her. The installer asks for the type of textures and if you avoid the 2048 ones, you should already be able to reduce the impact. Sooner or later you may use the external view, so that's where the impact happens regarding those textures.

 

Are "reduced textures" also VC cockpit and 2D panels textures?

 

 

 

Why would you create a piece of software that loads stuff into memory that you may never actually see on your flight?

 

Because FSX is an old game with 20 years old heritage code. When this code was written nobody imagined UHDT textures, 8 cores CPUs, 6 GB VRAM graphic cards etc. Simply FSX code struck its end and maybe that is why Microsoft fired ACES studio because new FS would have to be coded from scratch making it very costly to develop.  

Share this post


Link to post
Share on other sites

Thanks guys,

 

@B247NG: I have just looked at the working memory for FSX.exe in Task Manager processes. I did not even check my MD-11X or NGX, never had a OOM with all scenery enabled, flying for hours, but I'll sure do that as soon as I find the golden spot for Concorde :)

 

@CoolP: Very good idea, didn't think about that, I'll uninstall and reinstall with the lower settings set after I have tried the Ezdok and DLL stuff. Thanks for the DLL insight, very good info, I'll look into this. I have to do all this tinkering carefully, I would hate to do something I can't reverse, my rig is so rock solid in every other scenario :ph34r:

 

I'll keep posting my findings here.

 

Onwards and Upwards :)

Share this post


Link to post
Share on other sites

.. but FSX seems to load just about everything this side of the galactic centre! Surely that's crazy?

I can understand that it is trying to cache certain items. Where I get stuck is the fact that it doesn't really drop unused bits and, later, stumbles over the own rough housekeeping routines. The FSDeveloper article also mentions a kind of fragmentation. http://www.fsdeveloper.com/wiki/index.php?title=OOM_Error

 

Adding to it and stressing your point, it really accesses scenery parts from light years away if you keep them enabled. One can track it with the performance monitor and I couldn't see the pattern, like e.g. generic parts, which would make sense. Indeed, that method does look crazy for a program only having access to limited 32bit resources.

 

Besides, good points from you folks on the boxed product. I somehow thought it was returnable. Guess we should praise the F1 policy more often. B)

 

Are "reduced textures" also VC cockpit and 2D panels textures?

No, the internals should stay nice and sharp. The default texture size only affects the external appearance to my knowledge. So the impact on any kind of camera view for things like the pushback or cruise will be smaller. Must admit I never saw the downside of the 'normal res' textures in regard to the 2048 variant. :unsure:

 

I'll keep posting my findings here.

Lets hope it works out. If not, I feel your pain. :(

Share this post


Link to post
Share on other sites

Seriously, I can understand your concerns.

 

That's why I finally chose A2A B377 "Stratocruiser" as my next airliner. At least this one is very light on FPS. Besides I figured out that Concorde-X installation may corrupt PMDG planes' failure generation systems.

Share this post


Link to post
Share on other sites