I have all of Milton's planes and love them all. I have no problem with frame rates in the VC's of any aircraft (FS-9, 4 gig ram, Radion 1800 vd cd. AMD Dual Core). I can run with the sliders all the way up 30 to 40 FPS but for some unknown reason the VC in the Grzzly brings my computer to its knees, 5 to 8 FPS. When I pan up or away from the instruments it pops to life again. Just tried version 2 exactly the same. Any Ideas? Must be some mysterious glich. I got to fix this, got to have this great plane.
Wow Davery! Sorry to hear that you are having these issues.
Sounds like some gauge is causing the problem. Just checked on my new rig that I keep locked at 35 FPS and that's where she stays. So, how to isolate and find the problem ...
Since its likely a gauge issue the way you describe it, let's do a quick problem search using a process of elimination.
Make a copy of your panel.cfg and set it aside because we will butcher this one in problem determination.
Open the Panel.cfg.
Near the bottom are three vcockpitnn sections.
Delete vcockpit03 section; save the panel.cfg but do not close it.
Start FS and bring up the Grizzly.
If you still have the problem, then in the panel.cfg, select Edit and Undo to recover the deleted vcockpit03 section.
Delete vcockpit02 section; save the panel.cfg but do not close it.
Reload the Grizzly.
If you still have the problem, then in the panel.cfg, select Edit and Undo to recover the deleted vcockpit02 section.
Delete vcockpit01 section; save the panel.cfg but do not close it.
Reload the Grizzly.
If you still have the problem, then in the panel.cfg, select Edit and Undo to recover the deleted vcockpit01 section.
When you discover which section is causing the issue, do the following:
Delete half the gauges in that section and save the panel.cfg.
Test and if no change, Edit and Undo the deleted gauges.
Delete the other half of the gauges.
Restore with Edit and Undo.
Once you have isolated the gauge group, continue to isolate until you find the offending gauge.
You can comment gauges out using a // before the line or before the gauge info like this:
gauge20=//ST_X38!AP Suction, 642,518,76,76 -or- like this:
//gauge20=ST_X38!AP Suction, 642,518,76,76
Once you have isolated the gauge, we can decide what to do about it.
If this technique does not eliminate the issue, then it may be a bad texture or alpha causing the problem.
I hope this helps.