Surrexen

It seems like the F-16's interior lights and screens are dim even when on full after the last update, almost like it's permanently stuck in night mode or something. Anyone else getting this? Edit: 2pm in Persian Gulf - hot start on the ramp.

You might need to update the DTC cartridge via ground crew and then reload the DTC information. Try that out and see if it fixes it.

Doesn't have to be TPOD on the other screen either, the HSD showing the map will also cause the AG radar to flash when the arc is narrowed down.

Can we please get a fix on this busted texture. It's annoying having to manually swap it over every update.

Can we get a fix on this missing texture please ED.

Fine on this end. Using a warthog .. default trim bindings were fine.

Sometimes I've had betty stop talking. For example sometimes when the config of the plane changes she doesn't say "warning', but then other times it does work. I'm not sure about airstart but ground-start hot doesn't seem to put the data cartridge in and load it, so I've had to make sure I enter the cartridge to pick up the weapon info before I take off etc.

Once you've entered a destination point, you can select it from the main UFC screen where it says FP-A, then on the right you can hit the arrow and type in the destination point number and it will give you the steering info on the HUD. Hope that makes sense.

Sounds like your rate of descent is too high. I have done several landings and haven't broken anything yet.

So long as you leave the generated lua files alone, just launch it as normal and it will continue on.

This. Also binds for external lights on/off, landing gear up/down, and dragging chute.

So is the datalink going to work with AWACS at some point in the future? Just checking.

v118 is up Changelog v118: - JF-17 added - UH-1H added - Radio call-in's for MQ-9 Predator aerial drones that can act as JTAC's for the called sector, be advised the drones will have to fly from near Khasab to the target sector to give some semblance of realism. The drones are invisible/immortal to make up for the travel time. - Some minor script adjustments

v112 is up Changelog v112: - JF-17 added - UH-1H added - Radio call-in's for MQ-9 Predator aerial drones that can act as JTAC's for the called sector, be advised the drones will have to fly from near Kutaisi to the target sector to give some semblance of realism. The drones are invisible/immortal to make up for the travel time. - Some minor script adjustments

Cool thanks fatboy, that will get us through the day lol We're going to need a radio presets page that we can set the channels to etc in the mission editor.

Anyone know how you tune this planes radio in?

Ah I was looking for keyboard commands for elevation. Under keyboard it is sensor up and sensor down. Got it under control now thanks! :thumbup:

Anyone know how to adjust the radar antennae elevation?

I'm happy you are enjoying it :thumbup: If only we had a real Korea map!

v103 is up which is just a minor change to some scripting.

v104 is up which is just a minor change to some scripting.

Yeah those groups are on carrier/base defence and are on a fairly tight leash for obvious reasons. They definitely do attack things that get within their set ranges. The F-16's often trigger 'border disputes' and as a general rule the fleet defence planes do a pretty good job of keeping the area around the carrier relatively clear. I had made a small change in the scripts to do with red/blue air in the last update that I actually think is making all the AI planes slightly less aggressive which I have undone and that fix will be out once I've got this JF-17 in the hangar.

You will need to adjust some things in the scripts, but the script doesn't care if it's running single player or multiplayer. When running in multiplayer, only the host needs to worry about the de-sanitization process as only the host machine will generate the lua files etc. The host machine will also need file permissions in the appropriate folders to be able to write the files out. All the usual things.

Yeah this is normal. The SA page gets it's data for SAM site locations at mission start (like the data cartridge was prepared before you click 'fly'), before the persistency script can remove the units from the map. Unfortunately, there isn't anything I can do about that one. Edit: I've just jumped in to look at the D/L of the Stennis Hornets, for me when I switch the D/L on for each plane it is set to 127. This isn't something you can set in the editor either so I'm not sure why it's showing up different for you.

Worth a try I suppose, but I've never had to do that.