If you recall, to be an “Insider for FS2020” you needed to create an XBox account and install the XBox client on your PC. All one has to do is go to the Downloads and updates page to verify XBox - even on the PC - is an integral part of MSFS. (See below.)
I’m not “bashing” or saying this is a bad thing. On the contrary, it may be a good thing. Overall I’m just very glad we’ve had MSFS to “play” with this past year, bugs and all.
The XBox account is needed even for PC games that don’t have an XBox version planned.
Totally normal for titles that are released by Microsoft directly and available via GamePass. XBox is their platform, not just the console.
Although I owned both Arrows and despite myself I caved and bought the Warrior today, as it’s the G/A aircraft I learnt on and have flown the most. I really feared it would be too similar to the Arrows but I’m glad I ignored my own advice. JF are sneaky though, because ideally I would only own the Warrior and Turbo Arrow. Although the gateway drug, I can’t help but feel the normally aspirated Arrow is going to get a bit forgotten about for me.
My fear was that the Warrior II wouldn’t offer enough variance to justify the purchase but it does, and happily it really feels and sounds like a Warrior. On balance I’d say it is definitely different enough to just about justify the cost if you’ve already shelled out for both Arrows.
2 minor gripes though;
As mentioned, the prop animation maybe needs work. I like the fact that it isn’t the same as in the Arrow (which of course it shouldn’t be, being a different type of prop) but certainly at low revs on the ground it maybe looks a bit agricultural.
The texturing in the cockpit is again disappointing. I think, to be honest, the same applies to the Arrow(s) but this is slightly worse. When you zoom in on the dash it’s just a bit ‘meh’. I know texturing on these releases has been done to death already and I get JF’s justification for the external methodology but I can’t help but feel the interior textures could be better.
On the whole though another great product from JF. Heartily recommended.
It doesn’t seem to matter what I set the fuel load to be, I always get the above. I have checked that I have the setting Unlimited fuel switched off. When I did try switching unlimited fuel on, it still stayed as above, where as in default C152 it sets it to 50%.
Definitely not getting that. The only time fuel load changes by itself for me is when I run the Neofly Career addon which of course is working as expected as Neofly is meant to change the fuel load to match what is set in Neofly.
Maybe your state saving is messed up. Try going to the tablet and turning state saving off temporarily.
I found this looking for tips for flying the Warrior at full gross weight. Excellent very detailed flying information and tips for Piper Cherokee aircraft in general.
Is there away of getting it to remember your Payload, as mine always seems to default back to pilot of 77kg and removes passengers. Fuel is remembered but not payload. I do have save state on.
If you didn’t buy it from the Marketplace, you could try editing the Weight and Balance section of the flight_model.cfg file. Funny enough, I just did that myself this morning, but, I haven’t tested it yet.
I was hoping to update the Weight and balance of the plane to match one of the planes that I fly, but realized I have no idea how to update the MOI’s… So I left it stock as a II, but updated the pilot weights while I was there. I don’t know if it will have the desired effect, though.
I record my fuel at the end of each flight then create a ‘new’ W&B each time I fly. The fuel reverts to 50% when anything is changed, so I know I’m going to have to manually input fuel % as well as pilot and baggage weight. Just part of my pre-flight now.
Would anyone know how to get the logitech switch panel to start the warrior? It seems that when the magneto switch is turned to start it doesnt hold long enough to keep it cranking for start. The Arrow starts just fine. Thanks
That is a sim issue. To get the aircraft to start realistically it needs longer to start then just a pulse from the switch panel. Real Pipers tend to take a few seconds to catch.
Two solutions:
flick the Logitech switch to start several times over a few seconds to keep it turning over long enough to catch
they have provided an alternate file " engines.cfg_HoneycombYoke " for Honeycomb users that should work for Logitech as well that starts the engine faster, just copy it over the original engines.cfg