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.

I normally want to stay out of here, but I think over at FSLabs forums my opinion is going be even more "noise", so here it goes: First, I was one of two who got the refund after OOM using 4k monitor(s), so for that I appreciate the support I got. And looking at the forums I do not doubt the quality of support being offered. Second, its 2016 now, and many folks would be on 4K or DSR or mving to 4K or using mutliple monitors at 1080p. So its very important to know the limitations of this product in these cases. While its now on the product page, I cannot understand why the thread OOM thread was removed. I could understand if FSLabs wanted to remove their offer of refund (made in that thread, to at least Rob), so that more people would not ask for refunds if they were in similar situations. But that could have been stated there in the thread itself, that refund was offered only to people who bought before the high-resolution limitation was put up on the product page or state that offer was only to Rob as a one one time exception and no refunds policy stands for everyone else. We can still argue as why "no refund" if the product does not work as expected. Third, is the VC. I have not seen/used the earlier versions of ConcordeX so I had no idea of the VC quality. I just assumed for a $90 product it would be stand up to similiar priced products (hint hint). And that's my fault. Let me just say the VC is pixelated mess. The youtube video does not show VC in close-up for you to see this and the screenshots on the product page are a very low resolution. I don't have it anymore, but I hope someone posts good quality pics of the VC for folks to get an idea before buying.

So I finally found the solution for me. If the sim is started with any other aircraft (default or other), and after load if I change the aircraft to 777 or 737, then the VC will not function properly. So I must choose the 777/737 at the startup scenario screen or load saved flight at startup screen (with 777/737 as saved aircraft) to have VC working. Having any other aircraft loaded first will cause VC issues. Hope this helps others.

So I finally found the solution for me. If the sim is started with any other aircraft (default or other), and after load if I change the aircraft to 777 or 737, then the VC will not function properly. So I must choose the 777/737 at the startup scenario screen or load saved flight at startup screen (with 777/737 as saved aircraft) to have VC working. Having any other aircraft loaded first will cause VC issues. Hope this helps others.

Hi, I had tried these, also for the NGX issues: I have tried all these but no go: 1. Re-install the 3 simconnect versions 2. Run as Admin 3. Exclude P3D folder from active virus scans Regards Sandeep Katoch

I have the same VC issue with 737. Also 777 shows this problem, but only sporadically. Edit: I have tried all these but no go: 1. Re-install the 3 simconnect versions 2. Run as Admin 3. Exclude P3D folder from active virus scans regards Sandeep Katoch

I have these two issues: 1. On start-up of P3D is crashes (almost 80%) of the time with this in the Event Viewer: Faulting application name: Prepar3D.exe, version: 3.0.10.14945, time stamp: 0x560b4abe Faulting module name: PMDG_777X.dll, version: 1.0.0.0, time stamp: 0x55199a6e Exception code: 0xc0000005 Fault offset: 0x00283dc6 Faulting process id: 0x3438 Faulting application start time: 0x01d0fc91338f17cc Faulting application path: E:\Games\Lockheed Martin\Prepar3D v3\Prepar3D.exe Faulting module path: E:\Games\Lockheed Martin\Prepar3D v3\Gauges\PMDG_777X.dll Report Id: 8db9da99-6884-11e5-9c13-382c4abc46ce Faulting package full name: Faulting package-relative application ID: Once it starts crashing, I have to rename the 777 dll to something else, start P3D and then rename it back. Then it works for few starts, but comes back to crashing again. I have a ton of these crashes. Very frustrating. 2. If I load flight with 777 saved, many times the VC is un-clickable in 90% of the spots. Click on CDU to bring pop-up does not work, buttons don't work etc. My config: 4790K, 32GB, 980Ti SLI, Win10 Please look into these. regards Sandeep Katoch

Hoping its true. Can you try it out? My 3D vision trial has expired.

Some FSX only airports like Imagine Sim's VIDP perform poorly in P3D. Ideally the developer has to release a P3D version, but until that happens, there is a solution. I chanced upon this when I saw a solution to missing objects/buildings in P3D vs FSX as reference (e.g. Thai Creation Mumbai). Looks like there is difference in the BGL format for P3D vs FSX, this difference sometime causes invisible buildings or performance problems. The solution is to covert these BGLs to P3D format using ModelConvertorX. Step by step instructions on how convert a BGL are here - http://www.iflysimx.com/topic/1004-cuba-in-p3d-v23/. If I understood correctly, then you only have to convert library BGLs (vs placement BGLs). So the basic idea is to convert the BGLs in your Airport's scenery folder. Adventurous folks can use the batch mode to convert all/multiple files. I used the batch mode to convert VIDP and the result was that in the reference scene I was using to compare FPS, the FPS went from 10-12 to 22-23, almost 100% increase. Of course the actual result will vary for different airports, and in some cases you main gain nothing at all. Note that in the VIDP conversion, I was missing Jetways after conversion, so I restored only the jetway BGLs back to original FSX BGLs. So If you get missing objects you may have restore those BGLs. Overall, it is not completely straight-forward but the reward is worth it. For me, VIDP was un-usable before this, now its like any other airport. Lastly, I wonder if this can be used to improve performance for some Airports which support both FSX and P3D together. Maybe the developer keeps the BGLs in FSX format for dual compatibility and we can gain by converting?

Step by step here, in case you need - http://www.iflysimx.com/topic/1004-cuba-in-p3d-v23/

You can try converting the bgl files as described here, http://forum.avsim.net/topic/456188-fsx-scenery-airport-scenery-to-p3d/#entry3123635, it fixed Thai Creations Mumbai for me.