PA-28 Warrior II

@oscardelta59 Hi. I am not sure if you will get this message, but I will try.
You mentioned in your last message, that you found an issue with the extension in a file name.
As I am experiencing exactly the same issues as you mention, could you specify which file name you corrected, that allowed you to see your livery?
Thank you!
Regards,
Roberto

@lilycrose
Yes if it was only the gyro i could understand it, but when the alcohol compas also moves then….
Ill lodge a ticket, will let you know how i go 👍

@steveb Same base files - the difference is in the aircraft's geometry, which Asobo state in their SDK is 'critical' to accurate behaviour. The geometry is accurate in both aircraft, the difference lies in how Asobo's core flight model interprets it. Unfortunately, had this been FSX we would have had plenty of controlling coefficients to make the required adjustments.

As this game is set up, we have to take the accurate geometry and trust that the core flight model gets it right. When it doesn't? Well, that question has remained unanswered on Asobo's "DevSupport" forum for about a year now, despite numerous bumps . . . .

@martyn I have been using the GPS100, but I think I found the problem:
I noticed in another thread that there were some compatibilty issues with the GTN750. I had the free PMS50 GTN750 linked into my community folder though not selected in the EFB; when I removed it the autopilot started working correctly :)

The steps to reproduce the issue are the following:

Switch the radio panel on with the rotary knob Turn on the nav light in the alpha flight yoke The radio panel goes out and you need to switch off the nav lights in the yoke to turn on the radio lights with the rotary knob

@derek Fair enough. Thanks for the quick response!

@hetfild51 said in Piper 28 Warrior II - can´t use airplane:

@thtanner of course, i will try, when Microsoft releases new version.

Here is a screenshot, in MSFS i´ve got version 0.3.7. don´t understand :D

piper version.png

Different version of the software between the JF site and Marketplace, as outlined above. Your best bet will be to contact JF Support.

@europa27 thank you so much, now I only have to understand what lvar to use to set the lights for rev on, but I will make it :)

BTW this works a treat for both heading and course:

78ab25f3-1895-472f-ba09-d071ed16bfa3-image.png

@hama

Hi. There must be an avionics switch.

Finally, I got it working (after many hours), with this events : ELECTRICAL_CIRCUIT_TOGGLE, and "17" as value.

@hama ,

Thank you. The mod is already installed.

I think tis problem is solved now. I've deleted all entries like "PMS50", and when GTN530 is starting, i can see "version 1.1.2", the last version of WT GNS.

Is there a way to have the WT GNS Bezel ? Or shall we only see the Justflight's default one ?

@europa27 Oh, that is great news. I wish they would have published that more publicly. I am excited to see that update and then get the other PA28s

@tetley Com issue happened again today, and it happened with the same ATIS (from Salinas, CA) that it did last time. I never even tuned that ATIS, but I tried turning everything off and it kept playing over and over again. Is this is known issue? Thanks.

I too have this issue with the TDS gtn750. I’m experiencing sticking of the nav/gps in both gps and VLOC modes. Consequently when the gps auto switches to VLOC after reaching final fix on an approach I hear the click and see the change for a split second but then nav switch switches back to gps. I think if you cycle through the available gps modes via the tablet and then re selecting the gtn750 fixes this temporarily….
Btw I don’t have the PMS GTN750 installed.

We can't commit to anything at this stage but we are looking at possible avionics upgrades for our PA28s, including something like G5s, a more capable autopilot and engine instruments.

@crfactor my Garmin knobs in my 530 are off from where I put my mouse cursor. I have to place my cursor about 40 pixels or so above where I want to click for the buttons to highlight. But the knobs won't type text no matter what I do trying to enter a new airport destination. Just upgraded to ver 0.3.5 and can't say if the Garmin ever worked on older versions or not.