Any estimate for the Warrior update?
-
It's super unfortunate timing for me - I'm back to (real) flying lessons next weekend after several weeks of lockdown here and was going to crank out a few virtual circuits to get back into the swing of things :) Ah well - gonna have to re-remember stuff the old-fashioned way.
For the devs (from a fellow software dev): Please don't stress or work stupid hours to get this fixed - you all have lives and families and those are more important than us being able to pretend to fly a plane for a few days. It's fixed when it's fixed :)
-
@walterbeech First flight after the update it wasn't a problem until shutdown (so basically not an issue). But next time I loaded it up it kicked in a few seconds after starting. Like others here I could clear it by going to an external camera, but every time I went back to the cockpit it would reoccur within maybe 10-15 seconds. After that I didn't try again - went looking and found it was a common problem, so I can just wait for the fix.
-
I've eschewed flying it since the update as well, since a few things are wonky now sadly :(
Instead, I've started screaming around in the WT CJ4, which has just just slightly different flight dynamics :-P
-
It's been a couple of weeks since the last mention of an update. Are you waiting now for SU7? Just trying to get an idea of when it may happen. I've been flying the Hawk, which doesn't have the pop through issue at all, but it's not as satisfying as the Warrior. It's great at lighting your hair on fire, but it doesn't have the depth of the Pipers.
-
@katchaplin Try some high speed low level flight... 350 - 400 knots / 200 - 500 ft. This was at Bonnevile Salt Flats, a few miles West of KSLC...
-
@retiredman93231 Thanks, but I'm talking about things like OAT, oil usage, battery drain, even a Hobbs meter to track time. I'm trying to fly around the world in the Warrior, but I'm more or less stuck in Argentina until the graphic issue is resolved. The Hawk is fun, but it's not good for point A to point B.
-
My last flight was the worst, and we haven't heard any response from the Devs in 14 days, and even then only that they are aware of issues with SU6. They haven't acknowledged this specific issue at all. I'm going to submit a bug report and see if that at least gets a response.
-
-
This sticky makes it clear that new updates are coming - https://community.justflight.com/topic/2796/sim-update-6-issues
Nowhere have we said that we are waiting for SU7 and all the PA28 updates will be available next week.
The Hawk T1 was in the latter stages of development when a preview of SU6 alerted us to this issue and allowed us to fix it. The PA28s were already released so it's been more time-consuming to fix, and we have chosen to use the opportunity to address all the other feedback received since the previous update(s).
Hopefully the multiple PA28 updates so far (8 or 9 for the Arrow III?) make it clear that we have no intention of ceasing to update our aircraft.
Another developer has also made Asobo aware of this as it's ultimately a MSFS bug rather than PA28 bug, although we can work around it: https://devsupport.flightsimulator.com/questions/3560/exterior-and-interior-model-shown-in-the-virtual-c.html
-
@martyn Thank you, Martyn. This is really all I wanted, to know that you are aware of the visual issue and that you are actively working to fix it. My 'no more updates' statement was directed specifically at the comment above mine, not at your development team. I loved flying the Warrior, and I will again when I can see properly.
-
