February 2, 201610 yr Moderator I suspect resizing the 2D panels won't save us from OOMs either, right? Doubt it. if you're an owner of Concorde you'll get a more informed answer asking on the FS Labs forum. :wink: Ray (Cheshire, England). System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant. Cheadle Hulme Weather website.
February 2, 201610 yr I posted this FSLabs forums, can someone try it: I have a strong feeling that PANEL_STRETCHING=1 in P3d cfg file (which is a default value) is the cause of OOMs when using high-resolution screens (e.g. 3440*1440 or 4K). If I use this default value, then with the Beech King 350 2D panel, I can see memory going up quite a bit (by 150MB I think) and down as I increase/decrease my resolution (by resizing the window). And in fact, this resize action crashed P3d also few times. Now Beech King 2D panel is very basic so its surprising it can cause so much memory fluctuation as well as crashes. So I switched this option to PANEL_STRETCHING=0, and I no longer have memory going up nor any crashes. Can anyone with ConcordeX and high-resolution setup try this? (I don't have it anymore.) Anyway, we do not want the 2D panels stretched, they become un-usable on high resolutions.
February 2, 201610 yr Hi Duke, I will give this a try right now, I run at 3440x1440. Will report back. Allen, flight sim lover and AA-5 Traveler owner
February 2, 201610 yr I posted this FSLabs forums, can someone try it: I have a strong feeling that PANEL_STRETCHING=1 in P3d cfg file (which is a default value) is the cause of OOMs when using high-resolution screens (e.g. 3440*1440 or 4K). If I use this default value, then with the Beech King 350 2D panel, I can see memory going up quite a bit (by 150MB I think) and down as I increase/decrease my resolution (by resizing the window). And in fact, this resize action crashed P3d also few times. Now Beech King 2D panel is very basic so its surprising it can cause so much memory fluctuation as well as crashes. So I switched this option to PANEL_STRETCHING=0, and I no longer have memory going up nor any crashes. Can anyone with ConcordeX and high-resolution setup try this? (I don't have it anymore.) Anyway, we do not want the 2D panels stretched, they become un-usable on high resolutions. Duke, I am shocked at the results... I use a 34" 3440x1440 monitor. I just loaded one of my saved flights to keep things comparable, twice with =1 and twice with =0. This flight is the tutorial flight just before takeoff, I saved TUT_05 just after pushback with engines running. With panel stretching = 0, I literally, kid you not, save 400-900MB on VAS in this simple test directly between the two options, plus the panels are no longer stretched out of shape, and like you described, I can resize the window without the little blue circle appearing while P3D "thinks"... it's instantaneous. Behavior with the stock =1 VAS changes as I resize the window, smaller window, more free VAS, bigger window, less VAS. With your suggested =0, it loads (in my scenario and settings with 1.4GB free VAS) and stays around there, regardless of window size changes. With the Concorde sitting on the ground, zooming/panning/spinning camera, spamming 2D panels (8+ at a time), etc I can't get VAS to drop below ~1280000 using =0 at even a full size window running 3440x1440. By comparison, with Concorde sitting on the ground, zooming/panning/spinning camera, spamming 2D panels (same 8+ at a time), etc, VAS will drop down to ~388000 when using the stock =1 stretch setting. No idea if this will be different when flying, but this was the quick and dirty test using the same saved file. I will absolutely be running P3D with your suggested setting, as not only does it free up tons of VAS when using Concorde, but it also like you said keeps the panels from getting distorted regardless of window size. This was a fantastic find sir. Curious if others see similar results. I will post a couple screenshots of both settings showing FSUIPC monitoring VAS. Allen, flight sim lover and AA-5 Traveler owner
February 2, 201610 yr Duke, I am shocked at the results... I use a 34" 3440x1440 monitor. I just loaded one of my saved flights to keep things comparable, twice with =1 and twice with =0. This flight is the tutorial flight just before takeoff, I saved TUT_05 just after pushback with engines running... Wow! Thanks for the testing, four times I believe. I may yet fly at Mach 2! (But must keep my eyes off the INS
February 2, 201610 yr Wow! Thanks for the testing, four times I believe. I may yet fly at Mach 2! (But must keep my eyes off the INS Two quick pics to go along with my above post showing VAS difference: =1 (446528 VAS, this is default setting) =0 (1285980 VAS, this is no stretch Duke's way) Anyone else see similar results? Allen, flight sim lover and AA-5 Traveler owner
February 2, 201610 yr Will give it a try tommorow C. W. ,Ryzen 9 5950X @H2O , 32 GB RAM DDR4 3600 Mhz CL15 , Corsair MP600 Pro Watercooled 2 TB for P3D, Samsung SSD980 1 TB for Addons and Crucial MMX500, Red Devil Ultimate 6900 XT
February 2, 201610 yr Fascinating! I know I'm asking in the wrong forum, but since this seems to be the "live" Concorde thread - has anyone tested this (or can anyone test) in FSX:SE? I'd assume the impact on VAS would be similar but it'd be good to know for sure. Thanks in advance! Alan Ampolsk"Ah, Paula, they are firing at me!"-- Saint-Exupery
February 2, 201610 yr has anyone tested this (or can anyone test) in FSX:SE? Tried it in FSX-SE and it just kept locking the sim up. Tried every offered solution, no joy. Then yesterday, after some intervention from the Team at FSL which included a bit of TV input and control, they got it working, but when I re-tried myself, today, back to the lock-up. I think I might need to do a bit of Dll.xml editing. Rick Almeida
February 2, 201610 yr Two quick pics to go along with my above post showing VAS difference: =1 (446528 VAS, this is default setting) =0 (1285980 VAS, this is no stretch Duke's way) Anyone else see similar results? That's good enough proof. Now that I think of it, I had weird crashes going full screen from small window, and symptoms were same - round blue cursor and hang and then crash. These were with other planes. I think this probably fixes those also. Tried it in FSX-SE and it just kept locking the sim up. Tried every offered solution, no joy. Then yesterday, after some intervention from the Team at FSL which included a bit of TV input and control, they got it working, but when I re-tried myself, today, back to the lock-up. I think I might need to do a bit of Dll.xml editing. You also had OOM issues?
February 2, 201610 yr OOM issues Wish I could have even got to that stage. I could not even load the plane! It just froze the sim. Rick Almeida
February 3, 201610 yr I don't think this cfg option does anything in FSX-SE. My Concorde works fine in steam and I have never had an OOM with it. Mark CYYZ
February 3, 201610 yr I don't think this cfg option does anything in FSX-SE. My Concorde works fine in steam and I have never had an OOM with it. I was just going to report that FSX-SE has similar memory spikes as P3D when re-sizing windows and stretching=1. In fact the panel disappears on stretching (A321) and becomes unusable. So I believe its the same for both and must be very old flawed logic shared by both. With stretching=0 there are no more spikes. You might be trying with 1080p which does not show OOMs anyway. The problem manifests with high res monitors.
February 3, 201610 yr Doubt it. if you're an owner of Concorde you'll get a more informed answer asking on the FS Labs forum. :wink: Is there a way to get a refund if I'd run into OOM problems? I don't own the aircraft yet as I don't want to spend money on something that I know will slaughter my sim
Create an account or sign in to comment