Yup,
FlyingIron for sure. The only other developer that I don’t feel I have to research their addons, and will automatically purchase upon release.
Same. FI products are now day 1 purchases for me, just to support and encourage the developer to make further warbirds!! (The FW190 is the one I’m REALLY waiting for - I can wait to have both the Spit and a 190 in my hanger!!).
Yes, I eagerly await FlyingIron’s German warbirds too. Bf-109 was also in that blog. I hope FlyingIron or Milviz offer a high fidelity A6M5 or other Japanese warbird as well.
Since FlyingIron will have historical ambassadors represented from both factions from the Europe/Africa theater, I’m hoping they will offer a balanced Pacific theater including both factions too.
It’s looking like FlyingIron is establishing themselves as the high fidelity virtual historical warbird preservation company. If this was indeed part of their business plan, one could also hope FlyingIron could possibly offer an Il-2.
Nevertheless, there is no doubt that the upcoming Hellcat is going to hold my focus for a while.
Really looking forward to this plane. After all the fine-tuning they’ve done to the Spitfire and P-38L, I’m really confident in this F6F-5 being amazing from Cold Start to shut down. Just finished watching Flying Leathernecks with John Wayne on HBO Max and I’m hoping we’ll get a preview video soon of the FI Hellcat.
What do people feel about WEP implementation in general? There are essentially two options:
The WEP is part of normal range of throttle, if you don’t have a physical detent in yours it’s easy to accidentally shift from normal throttle range into WEP range. This seems to be the way they decided to go on the Milviz Corsair.
WEP is not part of the normal range of the throttle and unless the WEP button is engaged any throttle will stop at the virtual detent on the simulated aircraft. This means that for those with an appropriate physical detent on their peripheral get nothing from simply moving past the detent. This is used on the Asobo F-18 for example (with afterburner, but similar thing).
Personally I’d much prefer the second method on two counts:
-
It’s at least theoretically possible to make the WEP to automatically disengage (as it actually did on e.g. Hellcat).
-
Those with physical detents on their hardware probably have more expensive gear in general and can probably be counted to be more heavy users who are comfortable with programming software. In addition it’s easier to program around to second method than the first one.
I have a Thrustmaster Warthog throttle with a custom 3d printed detent as I never got on with the default A-10 style detent, and I’d actually prefer the second option as well. The thing with detents is that every throttle has its own position along the axis where the detent is (or people like me have custom ones that change it) and every plane will have its own position where the afterburner/WEP/airliner throttle modes kick in so they rarely match up out of the box.
In DCS I don’t mind fiddling around with the axis curves to get everything lined up nicely but DCS has superior axis curve tuning and also each plane loads up its own separate controller profile whereas in MSFS the curve tuning is a bit more basic and I have to remember to manually switch around profiles and I’m very forgetful and lazy!
So in MSFS in planes that have detents they rarely match up with my hardware anyway and it can be quite easy to drift into the AB/WEP zone without noticing it sometimes. So for me at least, it’s a lot simpler to just be able to firewall the throttle and then press some button I have within easy reach on my throttle grip. And as you say, most of these controllers come with software that let you program key commands to certain ranges of the axis anyway or people can use third party software to do it.
I prefer method 1. I never push my throttle to the stops in the Warbirds I fly. I expect the throttle to work like the real one and would not be happy having to push a button to activate the WEP.
You can easily program around that though. It’s a common feature in programming apps (including free and universally compatible Joystick Gremlin) to allow placement of virtual buttons on specific positions or ranges within an axis. Just bind a virtual button to WEP (or afterburner) once your physical throttle moves into the range it’s supposed to activate at.
It’s comparatively harder (though I don’t think outright impossible) to make a virtual detent from nothing.
I would just like the F6F released
Any update on release?
Probably after the holidays when people are back to buy it, and after SU10 to make sure the SU doesn’t break anything
Do you mean summer holidays for Europeans and Americans? Not Christmas, surely. I mean SU10 is now coming in mid-September, so hopefully end of September?
We are currently aiming for September 9 (website release), and marketplace a few weeks later
Excellent news!
While we wait… Here’s some light reading to tide everybody over.
A few F6F Flight Manuals while we’re at it (some might be duplicates, I didn’t check).
Yep, looks like another winner from the team at FlyingIron. That’ll be a quick buy from me when it’s released.
Looks on par with their others. In other words, instabuy
Hope we get a British plane “next”
Quite the opposite
Hahah fair enough! 2-1-1 for countries. I was just looking for some OCD balance in my life!!! Oh well, they quickly need to make 2 more after that to settle things