I have just signed up in their forum and waiting to be accepted. Those stutters are quite unique and only happen with the Concorde. With other planes like the Dash 8 I have far less to almost no stutters at all except when the framerate drops at highly detailed airports, but that is normal.

 

 

I have yet to test this as I also run EZDok. It sounds like this really could be the issue because even with a locked framerate of 30 the stutters are there, no matter where I fly. This can be over the ocean at FL570 at Mach 2 or during takeoff/approach in dense/less dense areas. As long as the aircraft sits on the ground unpowered it seems to be a lot smoother.

 

Let me know how it turns out on your computer with EZDok off. I´ll dig a bit more at my end tonight.

Let me know how it turns out on your computer with EZDok off. I´ll dig a bit more at my end tonight.

 

Did some testing and the results are identical. Disabled EzDok in exe.xml and played around a bit, smooth as silk. Also posted this in the thread over at FSLabs.

Did some testing and the results are identical. Disabled EzDok in exe.xml and played around a bit, smooth as silk. Also posted this in the thread over at FSLabs.

 

Looks like you have your answer then. If you still want internal views SimpleCam might be a reasonable alternative. It has no external views but the nine internal views it gives me has no impact on fps or smoothness. Available for around $10 from Avliasoft here.

Did some testing and the results are identical. Disabled EzDok in exe.xml and played around a bit, smooth as silk. Also posted this in the thread over at FSLabs.

 

"Good" - then we are on to something! (I have litteraly no hair left - the stuttering has caused two Windows re-installs, two months of sleepless nights etc.. :wink: )

 

As mentioned on the FSLabs forums, I made a tread about this over at the proper EZDok forum:

 

http://www.simforums.com/forums/ezdok-1187-fslabs-concorde-x-stutters_topic55490.html

 

 

 

Looks like you have your answer then. If you still want internal views SimpleCam might be a reasonable alternative. It has no external views but the nine internal views it gives me has no impact on fps or smoothness. Available for around $10 from Avliasoft here.

 

I'll buy it and test it right away. Costs nearly the same as beer here in Norway, so what the heck

Looks like you have your answer then. If you still want internal views SimpleCam might be a reasonable alternative. It has no external views but the nine internal views it gives me has no impact on fps or smoothness. Available for around $10 from Avliasoft here.

Thanks Ray, I will have a look into this if there won't be a fix for ezdok although I'd much more prefer a solution to the problem

Thanks Ray, I will have a look into this if there won't be a fix for ezdok although I'd much more prefer a solution to the problem

 

if you suspect SimConnect is being overloaded try running without ASN and see if that makes a difference. If it doesn't then the EzDok author needs to think about reworking his program for complex aircraft.

 

I'm really pleased with SimpleCam because its footprint is negligible and cockpit view changes are all I need.

Unfortunately I haven't flown with ASN yet, so the problem must be EzDok alone :(

Hi Max,

 

Being I'm not too used to 2D panels, how would I go about doing what you propose?  The easy solution is to load in a 1/3 sized window, and then scale to full screen while panel stretch=0.  This would keep all the panels the size you are after and keep VAS usage way down.

 

On a positive note, FlightSimLabs has acknowledged this as a recommended tip if wishing to run at a higher than 1920x1080 resolution.

 

It is working great for me running at 3440x1440 if I first load at a lower res window at launch.

 

A bit late but if you're still after a 'better' solution for the resizing thing.. I took the time and resized all those 2D panels in the panel.cfg to 1/3 of their original size (horizontally) and later tested with both panel.cfg's. Result: Jackpot. Resizing the panels in the .cfg does the same as starting P3D in a small window, then going fullscreen.

 

This is the scenario in which I tested: Concorde X loaded at Flytampa Sydney, RWY34R, AI traffic 10%, no weather, resized panel.cfg. VAS result after opening all the panels: 1GB left.

The same with the default panel.cfg: barely 500MB left.

 

EDIT: PANEL_STRETCHING can be left at 0, but at this point it doesn't really matter I guess.

 

If anyone is interested in my modified panel.cfg I'd gladly share it. Just PM me.

A bit late but if you're still after a 'better' solution for the resizing thing.. I took the time and resized all those 2D panels in the panel.cfg to 1/3 of their original size (horizontally) and later tested with both panel.cfg's. Result: Jackpot. Resizing the panels in the .cfg does the same as starting P3D in a small window, then going fullscreen.

 

This is the scenario in which I tested: Concorde X loaded at Flytampa Sydney, RWY34R, AI traffic 10%, no weather, resized panel.cfg. VAS result after opening all the panels: 1GB left.

The same with the default panel.cfg: barely 500MB left.

 

EDIT: PANEL_STRETCHING can be left at 0, but at this point it doesn't really matter I guess.

 

If anyone is interested in my modified panel.cfg I'd gladly share it. Just PM me.

Great, thanks for the follow up!  Went through a new system build since my last post, so look forward to getting some time again with the Concorde soon.