Felixthreeone
Charter Member
And I can live without the PFD in the 2D panel as I never use 2D panels anyway. So that at least is good to know! Thanks!
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
FS2004 Kodiak Build 2.0 is now released
- Thread starter Lionheart
- Start date
Man...
What in the world....
There used to be one thing that would cause this, and usually it would only cause the gauge (the PFD in this case) to not show, and that is for the gauge to be in the 'negatives' coordinates. And they are not. All are in the positive coordinates.
Another thing was sound files. And this uses no sound files other then basic FS2004 Caravan sound files. No button sounds, no unique clicks and things.
I'll keep searching...
Bill
What in the world....
There used to be one thing that would cause this, and usually it would only cause the gauge (the PFD in this case) to not show, and that is for the gauge to be in the 'negatives' coordinates. And they are not. All are in the positive coordinates.
Another thing was sound files. And this uses no sound files other then basic FS2004 Caravan sound files. No button sounds, no unique clicks and things.
I'll keep searching...
Bill
For those having FPS problems...
this will roughly halve the FPS hit if you go one way, almost remove it entirely if you go the other way...
Use Doug Dawsons View-skip gauge and totally delete from the panel.cfg the unused views! This will remove instances of the MFD and PFD you do not commonly use (depending on how you fly, you may delete VC or 2D panels - your choice) cutting down on the CPU load...
this will roughly halve the FPS hit if you go one way, almost remove it entirely if you go the other way...
Use Doug Dawsons View-skip gauge and totally delete from the panel.cfg the unused views! This will remove instances of the MFD and PFD you do not commonly use (depending on how you fly, you may delete VC or 2D panels - your choice) cutting down on the CPU load...
Hey guys,
I have a temp fix for those that are suffering from spoolup time on your Kodiaks.
On the newest version, engine tunes were carried out which put the proper factory RPM/Torque values/Fuel useages burn rates, etc into the equasion for instrumentation. They were a bit out of the ball park, and once tuned, were back in again.
However, when you effect one thing in an airfile/config file, you effect about 10 other things and it turned out the spool up time (increase of RPM from idle to full throttle, for instance) took a hit.
The temp fix (not fully tested) is to do the following adjustment in your Kodiaks 'aircraft.cfg' file.
* Navigate to your Kodiak folder in FS
* Open the 'aircraft.cfg' file with Notepad
* Scroll down to Turbine Engine Data section
* Change Fuel Flow Gain to 0.037
Example below:
[TurbineEngineData]
fuel_flow_gain = 0.037 // was at 0.009
This will bring the RPM increase to a normal rate. You can play around with the setting. That is the one on my bird presently. I need to test it for fuel burn to make sure its proper. It could 'possibly' be increased.
Thanks to the great guru Milton Shupe for this invaluable bit of information and also to Ron Freimuth for his pioneering studies in FS Turboprop tuning.
Bill
I have a temp fix for those that are suffering from spoolup time on your Kodiaks.
On the newest version, engine tunes were carried out which put the proper factory RPM/Torque values/Fuel useages burn rates, etc into the equasion for instrumentation. They were a bit out of the ball park, and once tuned, were back in again.
However, when you effect one thing in an airfile/config file, you effect about 10 other things and it turned out the spool up time (increase of RPM from idle to full throttle, for instance) took a hit.
The temp fix (not fully tested) is to do the following adjustment in your Kodiaks 'aircraft.cfg' file.
* Navigate to your Kodiak folder in FS
* Open the 'aircraft.cfg' file with Notepad
* Scroll down to Turbine Engine Data section
* Change Fuel Flow Gain to 0.037
Example below:
[TurbineEngineData]
fuel_flow_gain = 0.037 // was at 0.009
This will bring the RPM increase to a normal rate. You can play around with the setting. That is the one on my bird presently. I need to test it for fuel burn to make sure its proper. It could 'possibly' be increased.
Thanks to the great guru Milton Shupe for this invaluable bit of information and also to Ron Freimuth for his pioneering studies in FS Turboprop tuning.
Bill