Special Aircraft Service

Please login or register.

Login with username, password and session length
Advanced search  
Pages: 1 [2]   Go Down

Author Topic: F4U-1 FM  (Read 4705 times)

0 Members and 1 Guest are viewing this topic.


  • Stang Driver
  • member
  • Offline Offline
  • Posts: 330
Re: F4U-1 FM
« Reply #12 on: August 27, 2015, 07:40:48 PM »


First I'm glad you got some of the planes working.  That's why I include the ini & ru files in the adders ... so you can do a selective install of just the planes you want and you don't have to download all of them. 

On your installation problems the only thing I can assume is that some how you got a corrupted download.   I just re-downloaded the first adder and it installed perfectly.   Also the first adder (#WAW_1st adder m12) has been downloaded almost 200 times and you are the first to mention this problem.   Since I can't duplicate your difficulty all I can suggest is that you re-download the adder and try again. 

Wish I could've been of more helpful ... tooslow


  • member
  • Offline Offline
  • Posts: 54
Re: F4U-1 FM
« Reply #13 on: August 30, 2015, 02:04:47 PM »

Here's the last line of the log file which I assume to be the problem;

[7:59:36 PM]   FM called 'FlightModels/Bf-109K-14.fmd' is being loaded from Alternative File: 'gui/game/buttons'
[7:59:36 PM]   FM called 'FlightModels/Bf-109Z.fmd' is being loaded from Alternative File: 'gui/game/buttons'
[7:59:36 PM]   Main begin: PlMisAir: class 'air.BF_109V48' not found
[7:59:36 PM]   java.lang.RuntimeException: PlMisAir: class 'air.BF_109V48' not found
[7:59:36 PM]      at com.maddox.il2.gui.GUIQuick.fillArrayPlanes(GUIQuick.java:1064)
[7:59:36 PM]      at com.maddox.il2.gui.GUIQuick.<init>(GUIQuick.java:1841)
[7:59:36 PM]      at com.maddox.il2.gui.GUI.create(GUI.java:160)
[7:59:36 PM]      at com.maddox.il2.game.Main3D.beginApp(Main3D.java:1885)
[7:59:36 PM]      at com.maddox.il2.game.Main3D.beginApp(Main3D.java:1579)
[7:59:36 PM]      at com.maddox.il2.game.MainWin3D.beginApp(MainWin3D.java:212)
[7:59:36 PM]      at com.maddox.il2.game.Main.exec(Main.java:432)
[7:59:36 PM]      at com.maddox.il2.game.GameWin3D.main(GameWin3D.java:235)
[Aug 30, 2015 7:59:36 PM] -------------- END log session -------------

So if my assumption is correct and the missing 109V48 is the problem, what is the solution?


  • member
  • Offline Offline
  • Posts: 317
Re: F4U-1 FM
« Reply #14 on: October 24, 2015, 06:03:59 AM »

In real life the F4U Corsair was a pig to fly. It had horrible handling characteristics and pilots that transferred from the easy to fly Hellcat hated the F4U, even though the F4U was considerably faster. Corsair pilots used to call the F4U the "Hog" as well as "the bent-wing widow maker" because of all the handling related accidents the F4U had.

In fact, pilots had such trouble with the Corsair's handling that the US Navy first thought it to be unsuitable for carrier operations. The first F4U's were therefore restricted to land operations. It took some extensive training before the Corsair could be used on carriers. Even then the F4U was known more as a USMC fighter than a USN fighter, with most Corsairs remaining land-based.

Turning dogfights were to be avoided at all costs in the F4U. Boom & Zoom tactics were the way to success for the F4U, making good use of its 400mph+ top speed at high altitude. The F4U's size enabled it to carry a considerable load of bombs & rockets, which made it especially good in the ground attack role.


  • SAS Team
  • member
  • Offline Offline
  • Posts: 1430
Re: F4U-1 FM
« Reply #15 on: May 10, 2017, 12:53:05 PM »

True for the early 1A model but completely wrong for the 1D and Dash4...
Maybe grab some better sources before stating such wrong things like "pig to fly" and stuff....
I recommend the VF-17 story or Norman Hanson's bio...
And I remember some great 5 minutes of talking to a British FAA Corsair pilot at Duxford a few years ago....he had some different memories and never used the word pig to describe the Corsair....
Pages: 1 [2]   Go Up

Page created in 0.02 seconds with 21 queries.