dukeav

I would also wait for FSLabs to confirm that this is a solution and they will support this before buying.

So looks like panel stretching is quite buggy. I think the approach of loading small screen first is fine, I usually load in a window so that while loading process is on I can do other things, and go full screen when done.

Interesting. Can you try with a new scenario from scenario screen instead of saved one? I recall seeing panels remembering their states in saves.

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.

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. You also had OOM issues?

Wow! Thanks for the testing, four times I believe. I may yet fly at Mach 2! (But must keep my eyes off the INS

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.

CS claims hundred of switches: Switches (180) - Guarded Switches (39) - Buttons (298) - Selectors (46) - Knobs (80) - Levers (9) Is there a count for ConcordeX? I somehow have a feeling that 2D panels should not cause OOMs, maybe it's some rogue texture. But I don't have experience in this.

If you go back few pages you will find another user had OOMs just loading at this resolution with default scenery.

Co-incidentally, the 1011 has a fully functional FE panel in VC.

P3D is set to 11520x2160 for full screen, which is the native resolution of the monitors. The distortion, which I think you refer to, is only the side monitors.

I think CS INS allows you to enter the waypoints if you like, I may be mistaken though, I was just following the tutorial flight. For ConcordeX it seems primary operation is via 2D panels, so VC is neglected. I got refunded and in-installed it, hence requesting someone else to post. What scaling issues are you pointing to?

This is my camera view of INS on CS 1011($10 when I bought it): http://www.mediafire.com/view/durmbz0to8glg3s/CS_1011_INS.jpg Can anyone post a similar pic of ConcordeX?

I was down to a single monitor as part of the trouble shooting to try and make it work, and many 2D panels removed from the panel.cfg.

I use 3x 4K 40" monitors, so I am probably zoomed in more than others. Apart from that someone should post a pic of the INS in VC, as someone would create a camera view in Ezdok or Opus, all I saw was pixels.