Bruce_D

This is happening with all the AI after landing not only the wingman.

Great News! My script worked, I just had to adapt it a little bit for the wingman. I’m just turn it a little more user friendly and then I will publish it! Do you want to test it to make sure that I’m not crazy? If yes, just send me a PM and I show the script! Tks

The same for me

Hi, Tks for the answer. Yes, They say “Binfo Fuel”. I have created a .lua script to prevent this for AI air groups, but I’ve never tried for my wingman. I will try this and post the results. Do you know which is the fuel level of the wingman when he says “Bingo Fuel”?

Hi, I’m not if it is an ED Bug, but when you send your wingman to refuel at the tanker, the F-14 AI stops engage bandits after refueling. I have a track that can be downloaded here: https://forums.eagle.ru/showpost.php?p=4361110&postcount=5 If it is an ED bug could you kindly inform then? Tks

Ok, Here are some more bad behaviors from AI in SC. Every single group goes to CAT1, even if the others are empty. At 8:14 am on the track file we can see the strange AI behavior after landing; they hit and destroy planes parked that are waiting to start the next mission. Hope this can help Download here: https://1drv.ms/u/s!ApQqE-qOFUw3tnfn7yz9WRlV5OhY?e=UBZeCS

About the blackouts, did you eat before take off? Jokes appart, the blackouts occured top me when I wasn't well aligned with the catapult. With SC I managed to align better and this problem stopped. Check if this is the problem

From Wednesday to Thursday, after the new patch, I was managing to have kills with the AIM-54 against the AI at a range of 34nm. But on Friday it stopped work again. I haven't tested it any more, my wife don't allow me to play on weekends. :cry:

I had the same problem. What I discovered is that some times after landing you have to rise the launch bar. After that you can engage the nose wheel again. Edit: IronMike was faster than me on the answer

Not only that, but F-14 has a strange behavior on the carrier. Bug.trk

Everyone who had posted on this tread is banished from the game. That's why you can not login! OMG, I have posted! I am banished too :doh: Hahaha

Hi, You can use an axis to DLC. You said that you don't have any axis left, so just use a modifier button during land to engage an axis that you are using for a different function to be a DLC axis. If you are interested and have no idea on how to do it, reply this and I can show you on how to do it with a step by step. For example: if your joystick has 3 axis, with a modifier they become 6.

Hi, I had the same question on this post: https://forums.eagle.ru/showthread.php?t=238778&page=6 Hope that can answer.

I have the same problem in single player not using the mod. I discovered a solution, but in your case it's not going to work, you will have to have a cold start. In single player, when it is working, go to the RIO position. Their you will see that the LIQ COOLING switch is on the off position. You can turn it on. The LANTIRN is going to work. When you land and rearm and refuel and turn off the LANTIRN you will have the same problem. To solve it go to the RIO pit and switch off the LIQ COOLING switch, turn on the LANTIRN. As soon as the LANTIRN is on, put the LIQ COOLING switch on the on position.

When you tune the axis there is a check box named slider. Mark it.

Try the same and increase if you think it is necessary. It is not necessary to try bellow that! Throttle: try a negative number with slider check. Mine is -15. Hope I could help

Try 25 with deadzone of 4

When you adjust the curves you will feel the difference. Follow the other guys tips, they are very good too!

Hi, First: set wings to bomb mode. Second: Did you set the axis curves for your joystick?

Open beta and having no problems with DLC

Which is your step by step before activate DLC?

You have to use the emergency gear Handel to activate the gear. I almost lost a campaign mission because of that :mad: hahaha

Ok, This is the same problem that the Mig-23 has. Even the original F-16 skins has this “0”. I found the other solution just looking on the original ‘description.lua’ and looking for the nose and fin detail, but in this case there is nothing different from one update to another. Maybe someone with more knowledge then me can find a solution.

Great! Just be aware that this post has been reported. When they fix it this code will not be necessary.

Good that worked!