Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Making the FSX G-21 Goose Function and Fly Like the G-21 Goose

Featured Replies

Seems very nice. Will this work with the Grumman_Goose_G21A_HP or is it only intended for the stock FSX G21?

  • Replies 35
  • Views 16.9k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • The work is complete and the file has been uploaded to the library, called "goose_dynamics.zip".  I only just uploaded the file, so it may take some time for the file to show in the library.  If it's

Hi guys,So I followed the instructions in the readme, and since I have the OZx Goose Redux, followed those instructions as well. However, it seems now that the only Gooses (Geese?) that are showing in the "select aircraft" menu are the HP versions that aren't modified. What do you think caused this?

Same problem here. Everything looks ok in the cfg file, but there must be a full stop, comma or underline missing or in the wrong place somewhere. Ran out of time to find it last night. Will have to look closer tonight (unless someone else identifies and posts a solution in the interim!)

Check 'panel=' in the aircraft.cfg to ensure it is pointing to a panel folder. I had to add "A" (panel=A). Believe that is an OZx mod.

  • Author

Hi guys,

So I followed the instructions in the readme, and since I have the OZx Goose Redux, followed those instructions as well. However, it seems now that the only Gooses (Geese?) that are showing in the "select aircraft" menu are the HP versions that aren't modified. What do you think caused this?

 

 

Same problem here. Everything looks ok in the cfg file, but there must be a full stop, comma or underline missing or in the wrong place somewhere. Ran out of time to find it last night. Will have to look closer tonight (unless someone else identifies and posts a solution in the interim!)

 

 

Check 'panel=' in the aircraft.cfg to ensure it is pointing to a panel folder. I had to add "A" (panel=A). Believe that is an OZx mod.

 

 

Checking into it.  Those of you experiencing this please let me know if the fault appears when FSX itself is starting up, or if the issue is only apparent when you go to select an aircraft.  Also, check if a "panel" folder exists in the Grumman Goose directory (not a modified panel folder like  "panel.a" or "new.panel")  The original "panel" folder must still be in the Goose's directory for the installation to work.  If not, the aircraft will not initialize.

Seems very nice. Will this work with the Grumman_Goose_G21A_HP or is it only intended for the stock FSX G21?

 

It's intended only for the stock Goose, and the standard OZx Goose, not the HP version.

  • Author

Also, for those of you experiencing this, are the FSX default Geese still appearing as they should, and it's only the Standard, non-HP OZx Geese that are not initializing?

Hello Treetop,

I think Wendall and I are in the same, er . . . boat, in that having followed the instructions, we are only seeing the HP OZx models as selectable now in FSX.  And no, there is no obvious problem when FSX first loads. It's only when you try to locate the Goose to choose to fly it (so we can see how your new fdx files perform!) that you find the only ones you can see are the HP OZx ones.

 

I can only imagine that if you didn't have the OZx redux pack installed, at this point you might find you had no Goose(s) at all.

 

Then again, if Labrador is on the right scent (sorry, couldn't help myself) it may be the Panel/Panel A renaming instruction that is causing the problem (?).  Hopefully it will be an easy fix.


Ok, just went into the files again and I think I can see the problem. 

 

Following the instructions leaves the 'panel' file we're now trying to use (that is, for default and non-HP OZx textures) only containing the (new) .cab file.  I suspect it also needs the various .bmp files from before. I'll copy these back in and see how it goes . . .

Ok, all is revealed. Seems I (and maybe Wendall too) have not followed your instructions to the letter and have copied the 'panel' folder, air and cfg files in manually, rather than copying the higher level  "sim objects" folder and overwriting when prompted. 

My apologies for raising a problem mostly of my own making.  :blush:

 

So now I'm off to try your upgrade . . .

Well hats off to you, Treetop.  This is a great upgrade. I haven't tested extensively, but my primary desire to avoid the right-leaning tendency immediately after take-off has been granted, and the Goose now flies with a nicely balanced feel.

 

I did try taking off from a land strip and a spb. At the latter, I noticed that the usual Ctrl+W activation for the water rudder(s) didn't seem to be working. I checked the new v old cfg files and tried commenting-in (i.e. removed the // in front of) contact point 9. This seems to have worked to get the water rudder back again.

 

Will post again if I find anything else noteworthy, but for now, my sincere thanks for your excellent work, Treetop!  :drinks:

 

 


Following the instructions leaves the 'panel' file we're now trying to use (that is, for default and non-HP OZx textures) only containing the (new) .cab file.  I suspect it also needs the various .bmp files from before. I'll copy these back in and see how it goes . . .

Just checking in before doing something else to these files. Portia, is this the only thing that you found to be the cause of the problem? So I should just dig up the old .cab file and put it back in the panel folder. Also, should I keep them both (the .cab files) in there?

Just checking in before doing something else to these files. Portia, is this the only thing that you found to be the cause of the problem? So I should just dig up the old .cab file and put it back in the panel folder. Also, should I keep them both (the .cab files) in there?

Hi Wendall,

No no, don't do that. You need Treetop's new .cab file to get the properly working fuel gauge. It's not the .cab file that is the problem, it's the several .bmp files + the 'panel.cfg' file that were previously in the Goose's 'panel' folder that you need to put back in.

Hi Wendall,

No no, don't do that. You need Treetop's new .cab file to get the properly working fuel gauge. It's not the .cab file that is the problem, it's the several .bmp files + the 'panel.cfg' file that were previously in the Goose's 'panel' folder that you need to put back in.

Alright got it. After I'm done with the flight I'm doing currently I'll test it tonight. Thanks for the clarfiying!

  • Author

Just checking in before doing something else to these files. Portia, is this the only thing that you found to be the cause of the problem? So I should just dig up the old .cab file and put it back in the panel folder. Also, should I keep them both (the .cab files) in there?

 

 

Hi Wendall,

No no, don't do that. You need Treetop's new .cab file to get the properly working fuel gauge. It's not the .cab file that is the problem, it's the several .bmp files + the 'panel.cfg' file that were previously in the Goose's 'panel' folder that you need to put back in.

 

 

Ah.

 

When backing up before installation, did you copy and save the backups, or did you backup by renaming the files?

 

At any rate, perhaps I should have done a better job at explaining in the readme that the panel folder that is already be in the Goose's folder needs to remain there for the installation to work correctly.  The "panel" folder in the installation package contains only the .cab file.  It does not contain the panel.cfg and none of the bitmaps, so when installing it must be merged with the panel folder that is already in the Goose folder.  Otherwise the aircraft will not initialize.

  • Author

 

Well hats off to you, Treetop.  This is a great upgrade. I haven't tested extensively, but my primary desire to avoid the right-leaning tendency immediately after take-off has been granted, and the Goose now flies with a nicely balanced feel.

 

I did try taking off from a land strip and a spb. At the latter, I noticed that the usual Ctrl+W activation for the water rudder(s) didn't seem to be working. I checked the new v old cfg files and tried commenting-in (i.e. removed the // in front of) contact point 9. This seems to have worked to get the water rudder back again.

 

Will post again if I find anything else noteworthy, but for now, my sincere thanks for your excellent work, Treetop!  :drinks:

 

Thanks.  Glad you like it!

 

The reason why water-rudder activation didn't work is because the Goose doesn't have a water rudder.  Gotta use differential throttling to turn in the water, though applying full-rudder does help once you get moving a bit.  

Thanks.  Glad you like it!

 

The reason why water-rudder activation didn't work is because the Goose doesn't have a water rudder.  Gotta use differential throttling to turn in the water, though applying full-rudder does help once you get moving a bit.

 

Yes, of course it's a solid 'hull' so it wouldn't have water rudders. Guess we were just spoilt with the effect of water rudders in the default Goose. Will have to work n getting out of that bad habit.

  • 1 month later...

Thank you for this up date for one of my favorites. It really flys much more like the real plane. I do have one issue. I can't land on water with out crashing! I land with out flaps and with flaps at 50 and 100 percent.

However when the speed gets to 60 the stall speed it crashes! I see the SPLASH text and the flight is over.

 

I have tried landing on water at all speeds I can, but when it gets to the magic 60 knots it crashes.

 

Is there anything I can do to prevent this? I am using FSXA stock plane

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.