Yeah, the way the plugins are designed, you choose one shader only for each material. And the screenshot I posted yesterday lists all of the options that are available to the windshield extension. Very limited. I’m sure we’ll get more options over time, or people will come up with some simpler workarounds than modifying the gltf directly.
Hi, and thank you to the developers for this great plane. I fly in VR and wanted to provide some feedback.
-
In all the other planes that use the G1000, G1000 NXi, or the G3000, when the aircraft is within range and approach is selected, the autopilot switches from GPS mode to GS mode and attempts to capture the localiser whose frequency is active in 1. This is reflected on screen with the magenta GPS signal changing to the green Loc1. From here the autopilot will successfully capture the glideslope to the runway. I have never got this to work in the F-22. When selecting approach it always switches to Loc2 instead of Loc1. Even if the same frequency is correctly made active in both Loc1 and Loc2 the F-22 follows the general course but never captures the glideslope and descends. This is unlike all other MSFS planes in my experience. Eventually I managed to get this working by manually changing the CDI source from GPS to NAV1, and then selecting approach. Only then does it capture the glideslope and descend correctly, but still the ILS signal is off at some distance to one side and never in line with the runway. I have to manually fly the plane and align it to the runway.
-
In the drone camera view, when the drone follow mode is toggled (TAB or Xbox Right Stick), the engine sounds continue despite the plane not being visible. With all other planes in MSFS the sound changes and fades slowly as the aircraft becomes more distant until there is total silence.
-
The relative altitude display is crammed and difficult to read. In fact, it can even be misread as the first digit seems partly hidden.
-
VR cockpit zoom does not work at all in the F-22.
-
Apart from the normal display there is no warning if the gears are not retracted even in high speed flight.
Hope you can take this into consideration. Thank you.
I agree that the logic doesn’t function correctly to activate approach mode. The code for that logic was taken right out of the default G3000 PFD and unmodified at the time I sourced it. It could have been a bug in the G3000 at the time, that has been corrected since. It’s on my list of stuff to investigate, but I can’t give a time frame right now.
For the sound limitations, we have to use the legacy sound system (wav files) which function differently than the modern, AudioKinetic-based system that the Asobo aircraft and big-name studios use. Unfortunately, there is no way we can afford to use a license for this software.
As far as the PMFD layout, it still needs a lot of tweaking to get everything looking better (I think you’re talking about radar altitude on the PMFD, right?).
There are some limitations regarding VR with this a/c. We just don’t have the resources or time to get it where it needs to be in that aspect. If I manage to get a hold of some VR equipment, I’ll look into it.
An indication of gear position is on the HUD. If you look for the speed tape on the left side of the flight path marker. The speed tape will only be there if the gear are lowered. Trying to get every warning for every specific event is kind of out of scope for this plane. If we can get to it, we’ll include them as they come up.
Please try to understand that it’s a freeware plane and we’ve put a great deal of work into it, to the degree that it’s much better than a lot of the payware aircraft out there. Imagine how much better an aircraft that we could put a price tag on would be.
Thats true!
The working HUD and Velocity Vector are the BEST of all jetfigters out there.
Landing the Raptor is easy as It should be, just point the VV and work your approach speed, the plane Will touch down where you Are aiming.
Thank you for your reply. You, Adam and DakFly deserve congratulations and appreciation for your hard work in freely contributing this plane to the community. I’ve recently started a world tour using just your F-22 so it is my main, or you could say, only aircraft at the moment. I hope my post didn’t reflect any negativity or lack of appreciation. I just wanted to provide some feedback to help improve the experience if at all possible.
Just some further thoughts to my previous post and your reply.
Indeed, the stock G3000 was buggy at the beginning and exhibited similar behaviours so it’s understandable. Have you thought about just incorporating the Working Title G3000 mod?
I may have complicated my description of the sound issue. To put it more simply, in the drone camera view, we have the same loud sound of the aircraft even though it’s not visible at all. If that is something code related that you can change then that would be good, otherwise if it’s a limitation of the legacy sound system you’ve described then that’s understandable.
Yes, it’s the radar altitude on the PMFD.
The VR focus is a standard feature of VR mode bound to the key combo (L CTRL + L ALT + F). All other VR key bindings work in the F-22 except this one, so was just wondering if something may be blocking it.
The quality of your work is appreciated, and if you were to produce a reasonably priced payware version I would certainly purchase it.
It’s been discussed, but I think it’d be best to not require users to have other mods installed to be able to use this plane. When I have time, I’ll look at trying to reimport the section of PFD code dealing specifically with that logic again to see if that changes anything.
We haven’t done anything that blocks any type of key combo or key events in the sim. I’m not sure why it’s not working. Like I said, I’ll investigate it if I ever get the tools to.
Thanks for the compliment and happy simming.
Thanks for this wonderful product. It is my favorite jet fighter on the sim.
Kudos!!!
Evan,
I expect an update for the F22 no later than 1 pm my time after the next update next week breaks everything again
Seriously I have noticed an issue with the plane pulling to the right when landing. Might just be a torque fix but I been too lazy to actually look at it lol
I haven’t noticed this behavior. You’re sure it’s not just crosswind that’s causing it? If you narrow down a culprit, I’ll look into it.
I don’t think the coming update will break as much as SU5 did. But if it does, we’ll get it back up and running ASAP.
Hope all is well.
I am not sure it is crosswinds as I have testing it with no winds and with live weather. I will try calibrating my HOTAS again see if that fixes the issue.
As for breaking things, you should never underestimate Microsoft, need I mention Windows ME, Windows Vista?
Lol, I still think Windows ME got a bad rap. I enjoyed it quite a bit. Vista on the other hand…
Hello,
I have been using the F22 for a while now, always with great pleasure. Very nice with VR headset in a canyon !!
I have a small cosmetic issue in my plane list, here’s what I see :
I tried to compare the manifest.json file with other airplanes, and saw no difference. I also launched the console when calling for the plane list, with no error. My folder map looks good and I already tried to re-install the plane.
Maybe someone knows how to correct this lack of Manufacturer / model display ?
[Edit] : there’s a link with my Fr localization… if I put the game in English, the issue is gone.
I figured it out… French localization not implemented.
Here’s my small contribution to the project :
f22a_frenchLoc.zip.pln (4.9 KB)
To install :
- remove the .pln extension
- unzip
- replace the layout.json file
- add the “fr-FR.locPak” at the same place as the “en-US.locPak” file
To devs : you could implement all localization by just add them in the layout.json and duplicate the en-US file changing just the ‘language’ entry in the file. No big issue if people have the English description of the plane instead of the ‘native tongue’ description. But no loc. ranks the plane at the first place in the list as it’s named as on my screenshot above.
Thanks for the help! We’ll check it out. Yeah, en-US was the only entry in the localization file, so that’ll definitely cause those issues. Thanks again!
My pleasure
I used the Wikipedia French page for the plane description… it will probably not match your original text.
On the off-chance you guys haven’t seen this, it’s an F-22 (test) pilot talking about flight controls and stuff. Can probably skip the first 15 minutes because he’s going on about flight basics vs a Cessna.
Might be helpful for advancing the plane behavior and look.
Absolutely! We got lots of good info from that video. A link to it is hiding somewhere in this thread from back close to when this project first got started. Thanks for sharing!
I’ve never been a fan of the f22
To me. it’s ungainly looking and unatractive, also I find digital pits uninspired and full fly by wire aircraft generally pedestrian.
So, cam anyone advise me why I like this mod so much?
I realise the limits of the sim and the classified nature of some of the systems but as a “fantasy” aircraft it really feels coherent and well thought out.
I can see it being my go to “explore large areas” aircraft.
I’m truly, hapilly surprised by this mod.
Good stuff, it’s really groovy.
We’re glad you’re finding something of value in our efforts, despite your general disdain for this type of militaristic and pragmatic piece of flying machinery. Thanks for the props!
Well, to be truly honest I may have over exaggerated a little but this mod has really struck a positive chord with me.
I am a fan of the EF2000 and the su-33 but the f22 never grabbed me in the past.
as of trying the mod, this has changed quite a bit.
I’ve just been googling about the “007” serial f22 and it’s upkeep and how some can look really scruffy and unkempt and this really appealed to me.
I still think she’s a weird looking thing but she’s growing on me.
keep up the superb work.