The Grizz is out!!

Wow, a thread revival. Since I last posted I have upgraded to a high-end PC.

Thanks again for this fine aircraft Milton! Mike :applause:
 
davery said:
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.
Click to expand...

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.
 
And of course the links are still busted...

Thanks Milton - I'll just be patient until the library's restored.
 
Milton, went that but route dose not appear to be a gauge or texture problem as far as the panel folder is concerned, as a matter of fact I can remove the panel folder and I still get the same result when I pan down to bring the the empty instrument panel into view. Made sure it was defragged, I use UltimateDefrag which cured this problem with Digital Aviation's Piper Cheyenne and the PSS 757, and we know these are not FPS friendly addons. I have never had a problem with frame rates with any of your great planes and I have them all. This is strange for sure.Thanks for the quick reply. Any Ideas will be appreaciated. Davery
 
davery said:
Milton, went that but route dose not appear to be a gauge or texture problem as far as the panel folder is concerned, as a matter of fact I can remove the panel folder and I still get the same result when I pan down to bring the the empty instrument panel into view. Made sure it was defragged, I use UltimateDefrag which cured this problem with Digital Aviation's Piper Cheyenne and the PSS 757, and we know these are not FPS friendly addons. I have never had a problem with frame rates with any of your great planes and I have them all. This is strange for sure.Thanks for the quick reply. Any Ideas will be appreaciated. Davery
Click to expand...

Then it sounds like a texture issue.

In reviewing all the textures, the only thing that comes to my mind is that there is extensive use of DXT1 Alpha colorkey textures. You might try converting them to a 16-bit format (or DXT3 with a white alpha).

If you do not know how to convert to a different format, let me know and tonight after work, I will do this for you and upload them to my website with a link to you.

If this works, as these are common textures to all liveries, you can simply copy them to all texture folders.
 
Grzziy Framerate issue

Milton I have no experience converting textures. If you find time I will greatfully take you up on the offer. I do love this plane. Davery
 
Grizzly VC framerates fixed

Milton :ernae:Thanks so much. You nailed it, 30 to 35 FPS in the VC. This baby is coming out of the hanger. Lets go flying. I think I saw earlier a post where some one else was having the same problem. Might be a good Idea to make these textures available as a fix for others. Thanks again Davery:applause:
 
davery said:
Milton :ernae:Thanks so much. You nailed it, 30 to 35 FPS in the VC. This baby is coming out of the hanger. Lets go flying. I think I saw earlier a post where some one else was having the same problem. Might be a good Idea to make these textures available as a fix for others. Thanks again Davery:applause:
Click to expand...

Great! Thank you for being concerned enough to raise the issues so that everyone who has this issue can benefit. :applause:

The textures fix zip is here:

http://www.flightsimonline.com/downloads/xa38basetextures.zip

For those who are having FPS issues from the Grizzly VC, these textures once unzipped should be copied to each texture folder of the xa-38, overlay okay.

For the technically minded, these textures were converted from DXT1 Alpha Color key to DXT3 with a white alpha. If you prefer and can handle higher resolution (larger video demand), you might convert the originals to 32-bit instead.
 
Milton, thanks for all you've done on this model as well as the fixes that got er running better for some of us. I know I had the low VC FPS issue back in the beginning which you tried to help with but I never got resolved until now. I forgot about it all whilst working on other flightsim things. All is well now and man oh man, what a gem this model is! :medals:

Thanks also to davery for the PM letting me know about the fix. :applause::icon29:
 
@deathfromafar: I apologize for not picking up on this sooner for you and others. I am very happy that you are good to go with this now. Thanks for you patience (and endurance).
 
Milton Shupe said:
@deathfromafar: I apologize for not picking up on this sooner for you and others. I am very happy that you are good to go with this now. Thanks for you patience (and endurance).
Click to expand...

Milton, no need to apologize Sir! When Davery sent me a PM related to this update, I suddenly remembered that I had forgot to follow up with you on the problem after you had tried to sort it out. That's my bad! Anyhow, as usual, you have done a great work for the community on both the model and helping sort out any bugs we had in an otherwise superb model. The thanks goes to you and all involved to help make it a great model!

:USA-flag:
 
You must log in or register to reply here.
Back
Top