-
There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.
If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.
Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.
The Staff of SOH
More Piaggio PD-808 models.
- Thread starter Ferry_vO
- Start date
I don't know how much you know about working with the panel config file, so I am going to go at this like you know nothing about it.....not meaning to be insulting, just helpful.
Here's a look at a standard line from a panel config.
gauge.1=RPM_1, 120,150,80
The first part "gauge.1=" is the code for calling a gauge and the sequence it is in in the panel config. The next part "RPM-1" is the name of the gauge being placed. Parts two and three "120,150" give the coordinates for the top left corner of the gauge in an X (sideways) and Y (up and down) placement from the top left corner of the panel. The last part "80" is the size of the gauge in pixels. SOmetimes you will see 2 number for size "80,70"....this will be for sizing none round gauges and tell how wide and tall the gauge is in pixels.
Make a back up copy of your panel config file at this point...because this is were you start messing with it.
To isolate the gauges one at a time to find out which gauge (or gauges) are causing your frame rate drops, you will need to change the line just a tab bit to look like this.
//gauge.1=RPM_1, 120,150,80
Placing the double slash // in front of the gauge line prevents the sim from reading that line. Start at the top and work your way down through the gauges, one at a time, until you find the one that causes your frame rate drop. If nulling out gauge.1 does not improve your frame rates, go back in to your pane config and remove the // and put them at the beginning of gauge2. Test again. It can take quite a bit of time and testing to find which gauge(s) are causing the frame rate drop. Be patient, don't fear messing wth the panel config (remember, you did make a back up copy of it..so if you trash the file so badly that it no longer works, you have your back up to fix things).
Hope this helps you find the problems with the frame rate drop. Again, I am not trying to belittle or insult you...but to help you improve your sim performance and enjoyment.
OBIO
Good approach OBIO.
I usually work with aircraft with a lot of gauges so I use the binary approach.
Back up the panel.cfg
Delete half the gauge entries and test.
If the problem goes away, I know which half its in.
If not, restore that half, and delete the other half.
Repeat the process.
Once the problem is localized, you can further do halve or use OBIO's comment out approach until you isolate the issue.
I have found that sometimes it's the gauge, but rarely. The issue I find is the gauge bitmap size versus the stated size in the gauge statement. A compass can really hit FPS if the bmp size vs stated size is off.
Hope this helps.
I usually work with aircraft with a lot of gauges so I use the binary approach.
Back up the panel.cfg
Delete half the gauge entries and test.
If the problem goes away, I know which half its in.
If not, restore that half, and delete the other half.
Repeat the process.
Once the problem is localized, you can further do halve or use OBIO's comment out approach until you isolate the issue.
I have found that sometimes it's the gauge, but rarely. The issue I find is the gauge bitmap size versus the stated size in the gauge statement. A compass can really hit FPS if the bmp size vs stated size is off.
Hope this helps.
Good looking plane - downloading now!
Daube
SOH-CM-2025
Thanks a lot OBIO. I'm very familiar with panel edition, and I do not feel insulted at all. In fact, I think it's cool that from time to time people make the effort to give simple details and explanation for important notions such as this one. You can bet your post has been very usefull for a lot of beginners that have read it.
What you have explained is exactely what I planned to do some months ago when I installed the plane. Unfortunately I had no time yet to investigate further. Seeing those screenshots gave me some more motivation to fly this bird, perhaps tonight when I'm back from the office I'll take a deep look into its files.
Hi Daube,
i have removed ALL gauges and the textures in the VC to see
if that would fix the problem. I did not. My PC still can handle
PMDG aircraft which is always my benchmark.
I finally got this one downloaded and ran a brief check. First of all. . .the dynamic checklist is the coolest thing I've seen in a while. Nice job there Mario. Initially, I moved around the cockpit and had no lags at all, everything seemed smooth to me. I had my frames locked at 25 (for MP purposes) and when I actually watched the fps count and moved around the cockpit it stayed at 18 to 19. . .changed to a different aircraft with similar cockpit environment and it went back up to 24/25.
Unlocked the fps to unlimited and the fps count went beyond 45/50. Nothing wrong with that, and to be honest, even the 18-19 fps wasn't anything i would consider significant enough to go hunting for the problem.
I don't know what the actual frame rate count was for the folks who are having that problem so I can't say anything concerning their specific problem, I just know that while there seems to be a drop when in the VC, it isn't enough to cause even a second look.
Unlocked the fps to unlimited and the fps count went beyond 45/50. Nothing wrong with that, and to be honest, even the 18-19 fps wasn't anything i would consider significant enough to go hunting for the problem.
I don't know what the actual frame rate count was for the folks who are having that problem so I can't say anything concerning their specific problem, I just know that while there seems to be a drop when in the VC, it isn't enough to cause even a second look.
Richard Westcott
Charter Member 2011
Fantastic aircraft. Thanks Mario.
Daube
SOH-CM-2025
In FSX, in a normal zone, this plane would make my FPS drop from 40 down to 10-15. The usual port-overs never exceed 10 FPS impact, this one has nearly a 30 FPS impact. I had no time to investigate yesterday, unfortunately :/
Wing_Z
Charter Member 2011
Well luckily for us, there is no problem in FS9!
Given the creative flair usually associated with things Italian, it's amazing they produced so many apparently pointless aircraft!
This is another one, very nicel modelled though - and I agree the dynamic checklist should become mandatory...
My ha'pennyworth of screens, vital to catch the unique main undercarriage retract:
Given the creative flair usually associated with things Italian, it's amazing they produced so many apparently pointless aircraft!
This is another one, very nicel modelled though - and I agree the dynamic checklist should become mandatory...
My ha'pennyworth of screens, vital to catch the unique main undercarriage retract:
Daube
SOH-CM-2025
I just tried.
Removed all the textures (the VC does not even appear anymore, like there's none)
Aliased the sounds to the Learjet
Aliased the panel to the Learjet
Removed all the effects and lights from the aircraft.cfg
And the plane is STILL bringing my FPS down to 18.... I DO NOT understand
Of course, in the external view, the performance goes back to normal. It's really just the VC model that's causing the trouble.
