FlyingAlex

If that's the case then it makes sense. I disabled all FCS while TVC was on so I could test what it can do. When using. TVC the AoA could easily go over 90 degrees

Indeed. The aerodynamic things are just complicated. I could hardly get into flat spin with my flight model now. Mostly I could get into a vertical spin if I pull the stick too hard with TVC. the plane loss speed very quickly and keep rolling nose up and down. I can easily recover with TVC but I don't know this behavior is normal or something go wrong.

@crixxx As it’s real EFM, I have to build up everything again so it would take time. I’ve tuned the speed at sea level and at altitude similar to the SFM we currently have now. But Lift and Drag still WIP. And I have to connect the cockpit so everything could show normal in cockpit. @mrjay it looks good, I would leave the FCS handle in lua instead of efm in this case.

For me it's too early. I will implement the FCS after I figure out a more realistic flight model. Both EFM or lua cockpit script will work as long as the logic is right. Keep it simple then lua. Want more details then EFM I'm going to fade out the compiled lua file which limited the functionality (and some binding). I would like to fade out the FC3 binding with more realistic control logic such as pressing button on mfd to control avionics instead of a keyboard button. If you have a solid one I'm of course happy to test it with TVC.

Hey buddies, I know you would be interested. TVC I was not bragging You can see the plane turning not smoothly. It's because of the AoA limiter is not well tuned. The whole flight model need a big tweak. But at least it WORKS! Hard to fly in 3rd person view. Don't know any supermaneuver move. You guy can suggest some of it and see if I can use those move to judge the performance of the TVC.

Great! TWS missile working. didn’t update dcs due to working on the EFM. Good news is, I have a EFM F22 with the old avionics flying now…. with terrible flight model having thrust vectoring as well but it will easily make the pilot blackout and it’s not fly by wire… have to press button to control the nozzle angle See if I could make a video demo this week. far from releasing as I could hardly fly alive for 5mins in it

Maybe you have made some mistakes broke the file.

What I am doing exactly is create new lua device script to override the old one as I have no intent to rework those compiled lua. I could enlarge the new added text for IAS/Heading/attitude. As the window for the hud is compact, those custom hud text couldn’t enlarge for so much otherwise the default f15c hud component would be overlayed.

I didn’t change the overall hud showing size. You see the hud size being small because of my zoom level setting.

Working on the font I installed the clear glass mod so the hud text is not as clear as it should be.

Custom hud is added as well. Will upload some screenshots

Can you notice the changes? Do you like this ? Multiple mfd monitors get useful now

As I found that I’m exploring on and on. The works I planned for F22A modding is growing so there are things I want to state first. I like the way @Nightstorm has stated with this enhancement mod. This is a community works and everyone should be encouraged to contribute. Thanks nightstorm for it. The changes I’ve made would continue to release as add-on and they will stick to this thread as I want to avoid any drama that would happen. We are all here for fun. No need drama. And keeping things in one place is good. As a software developer myself in real life, I always upload my code on GitHub for better documentation and versioning. It would enable others to contribute in a much easy way too. Github along with git are great and common platform/tool in the world of software development. I recommend it for everyone who code and willing to share. I want to give more information on the Weapon Bay page I'm making while it's in progress if I may. As you all may know, there is no way to obtain data from the FC3 module in a straight way. Everything is workaround and hacky trick here. The weapon bay page can have all the payload in the beginning of the mission in a straight way. However, it’s much more complicated to trace which weapon the user choose and which of it was released. For now it’s matching my control style but I need to think of every cases before shipping it. I’m thinking to rework the logic of entering each of the hud mode and selecting weapon as well. It will be a big changes of files actually so I’m still looking for the best solution for this. This weapon bay will be released once I thought it’s stable enough for everyone normal flight. It may take some time. In addition, for the funny landing story from Nightstorm ,here is my reply in the chat with Nightstorm Every landing you can walk away of is a good landing but a expensive landing it is. I think it somehow prove that the AoA for landing now is ok. Actually I think it’s very close to the feel land a FA18C with ATC. You may try a F2 view and compare with real life video Next time anyone who broke his gear in the mission like Maverick in Top Gun, ATC approach for a hard landing may be a solution. However, ATC would be disengaged if there is Master Caution in my recent update. I don't know is there master caution if your gear broken tho

The atc contains some code from the JAS 1.8.0 which was released to public on GitHub years ago. Since I talked to Whisky_actual on discord only, if whisky_actual you are reading this thread yeah this is my DCS forum account @Nightstorm I believe the moving map is a doable stuff with some precise calculation as we can have the aircraft coordinate through api. And a more proper map image of course. getting waypoint on it seems not possible. But we can at least put the airport on the moving map. We should be able to get awacs call data on our client export but have to find a way to communicate with the mod. Not sure possible or not. Love the community idea. The reason for me doing this was just want to get rid of fc3 avionics and for now make anyone happy would be a bonus for me

@Mike34 Bad news are RWR, SMS page won't be exported successfully. This is FC3 limitation. Good news is, you come into this thread in a right time. I am making a custom Weapon Bay page which can correctly show the payload. It's in progress but can show you a screen. I started the work yesterday and told nightstorm this morning. I'm happy the way I expected to figure it out working and the progress going fast. In the screencap, green dots are pylons with weapon, white dots are empty pylons, red dot is the weapon you are selecting. What I have to do is add the weapon name / abr on the screen. this custom weapon bay can show all the name of the weapon f22 can carry correctly updated Not bad for me, really sick of fc3 avionics as I want to export sms and rwr page too… this weapon bay page is not yet finished. And it need some new binding to replace the olds. I will try to see if I can make a rwr on my own. Seems possible. For the ICP, please export ICP page

ATC add-on update Due to my mistake on the MFD page config. The mfds were broken in my previous release. Thanks nightstorm for the testing. Lesson learnt. Would test with a clean build before next release. add-on updated with fixs: https://github.com/kingDevGit/DCS-F-22A-Auto-throttle-ATC

@mrjay As the original mod the creator bind the animation directly to the fc3 throttle bind. I need to create a new binding for throttle and point the animation to follow the new binding instead of FC3 throttle bind. I thought it's done in engine.lua which is encrypted. It can be decompile, not hard but it's time-consuming. For now I could leave it as it be first. Once I finished the new binding which is also mandatory for the throttle push/pull disengage trigger you suggested I may take a look. @Mike34 Good work! I need that ICP layout can you upload it I'm too lazy to download software for extracting it. Actually I do have helios profile showing on my screen while I was recording the video above. Just the nvidia software didn't manage to capture it. Simple stuff, just add code at the end of the init.lua in the corresponding folder of the screen you wanna export. Let's say center mfd: cockpit/scripts/MFD_CENTER/init.lua add this dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F22A_MFD_CENTER") In helios the viewport need to have the same name which is F22A_MFD_CENTER and click reconfigure monitor in helios. All done However, if you need to get the buttons work without binding keyboard press to it, you need a custom DCS Generic profile which I mentioned before. I don't know if you are already working on it so I just leave my repo link here so. you may use it if you need it. https://github.com/kingDevGit/DCS-Helios-Community-Mod-Profile. Please be aware I have physical mfds for left and right mfd so I had only exported buttons for ICP, center MFD, PMFD, L/RUFD and startup related bind which those I exported to touchscreens. Won't be hard to add yourself if you get the code meanings (They are well documented with comments ). If you could help to add left and right mfd buttons it would be great. You may create a pull request on github so I could merge it. @Nightstorm As I will keep updating this add-on. I've put it on github so everyone including myself can trace what's updating. I had minimized the files need to be replaced. I will add a remark to tell everybody no need to download on github again if they install your enhancement mod after you've merged it. I will also add a branch to indicate which version you are using. Feel free to tweak it and it would be great pleasure if you would create a pull request after you tweak the code so I can notice them FOR EVERYONE AS WELL ! if you cannot wait until nightstorm merge it to the enhancement mod. Install it yourself. AUTO THROTTLE MOD FOR F-22A Link: https://github.com/kingDevGit/DCS-F-22A-Auto-throttle-ATC Click Code->Download Zip Follow the installation instruction Features: Approach mode will keep the aircraft with AoA 12 degrees. With this AoA the aircraft could land with the posture very close to real life (Nose up, cushion landing with left right wheels first). So once you've engaged the ATC approach mode, slowly trim the plane pointing to the runway and the plane will keep an ON-SPEED AoA to land (around 150 knots in my test, 6 AARAM, 2 sidewinder, 610 gallons internal fuelcell). Your plane should be in a flare posture on the touch-down, slow your plane with the brake and slowing put your nose down. The FC3 mod have a bug on the nosewheel, you will find your nosewheel getting into the ground if you hit the brake too hard so kindly tap the brake to slow yourself down. Cruise mode will try to keep your existing true airspeed. Useful on AAR, cruise. The plane in this mod could accelerate very quickly so it could prevent the aircraft from draining fuels. Also because of the same reason (plane easy to go fast), ATC won't be useful on slow speed as even you pull the throttle all way down the plane can still keep the speed for quite a while or even accelerate if you point the nose downward. That's also why you need the speedbrake to maintain AoA in approach mode tho IRL F-22A do use the speedbrake while landing so it's close to realistic. Everybody, if you have any questions, suggestions or improvement works please don't be hesitate to comment. You may also create pull request in the repo above so we can all contribute. EDIT: I missed a file in the repo. Just uploaded the missing file. If you tried installing this addon in the past few hours please try again

@mrjay In F/A18C the throttle moves in ATC so I will keep it. for the second suggestion, I have several disengage triggers flaps position changes, touch down, engine failures… what you suggest definitely is a will do.

Hi lads, I want to share a simple personal work today which is a auto throttle (atc) mod for this mod. ATC have two mode Cruise - Hold existing airspeed Approach - keep AoA for landing Here is a video I recorded for demo: Now I am testing for a proper AoA for landing. It’s 7 degree in the video but I thought it should be around ~10 - 15 degree according to the real life F-22A landing video in YouTube. @Nightstorm see if you are happy to include this to your enhancement mod

Tested with old loft value. Missiles all fine with STT. Seems the lofting problem only exist on TWS. It looks like a missile lost a lock and found it’s target again while pit bull

I had built a Helios profile file for this mod. As I have two mfd screen, I exported only the buttons of ICP, PMFD and the Center MFD along with the APU, L/R Gen switches which I export to two touchscreen. Feel free to add the buttons you need yourself. You may find the file on my GitHub. https://github.com/kingDevGit/DCS-Helios-Community-Mod-Profile/blob/main/Helios_F22A.lua

Ok tested with different altitude. Reduce the factor to 0.35 did the trick. May still need to reduce the missile power. It’s so energetic

Tested several round with latest OB and only this mod installed. The missile still pull up too much if the target is over 80nm. I released AIM120D2 in 6 different distances Test with F22A angel 37 1.5Mach targeting at Mig29A angel 30 Mach 1 Hot 1st to 3rd launch which were ~120nm ~100nm ~90nm where mig 29A just entered the Rmax: missile climbed to ~180k feets and come down while mig29 was at 20nm close then overshoot. The missile was still at 100k feets high while it reach the mig29 coordinate 4th launch which the mig29a was at ~80nm, the missile climbed to around 90k feets but it managed to get down fast enough to splash mig29a 5-6th launch around 5-60nm the missile work normally I could attach a track file after work. Do you mind kindly take a look if it’s work as normal or something went wrong?

I haven’t played with F22A since 2.8.1 update stable but I update the mod as long as you release new update. I use git locally to keep track of the files changed so I shouldn’t mess up. I tried rollback to earlier version but no luck I am thinking if it’s the old loadout preset causing this issue but it shouldn’t be… Edit: Test with original F22 mod still no luck. Weird. Asked with original mod dev they said it was broken due to Aim120 guidance code update while 120D is the same missile without drag Can anyone with stable release confirm it? I better go for OB from now on and test again while the stable not really stable and there’s no advantage to use stable

Hi all today I fly in this F22 mod with the newest update but I found all the 120D/120D-2 I fired go straight to the space. Fired from 50k feets and the 120D went to 100k+ feets and of coz missed the target. I thought maybe some weapon conflict with other mods so I removed them but no luck Anyone have any ideas or experienced similar issues before? sidewinder works fine