Tiramisu

Das sieht so herrlich aus! Ist schon das Releasedatum bekannt?

I believe liveries are specific for certain countries. Do you have more information about this issue?

For testing purposes I let the mission run with AI only and then I let the time run faster. For long missions I try to recreate some situations. E.g. instead of letting the AI takoff from the very start I let them spawn near the objective, which is very helpful if you want to balance your mission. Furthermore you can write down the time stamps of important events during the mission and then compare it with the Tacview replay. For missions with lots of airplanes you can select one of them in the F-10 map and then watch its outside view with F2. So you do not have to switch through all available airplanes. At least you can add radio items to trigger certain things during the mission.

You are very welcome! I was also interested in how to deal with that target detect function. :thumbup:

Maybe instead of RADAR you have to use the enum like this: Conroller.Detection.RADARAlso getDetectedTargets does not return a table of objects. Instead it returns a table of tables that contain informations about the detected objects. More precisely you can look up the structure of the return value it in the documentation: https://wiki.hoggitworld.com/view/DCS_func_getDetectedTargets Last but not least you have used getTypeName in a wrong way. You should be very careful, before you start testing your scripts. Probably you should refresh your Lua skills a bit. :) So instead of your code I would try cmnd = Unit.getByName('E3') logi = Unit.getController(cmnd) list = logi:getDetectedTargets(Conroller.Detection.RADAR) for _,DetectedTarget in pairs( list ) do if DetectedTarget ~= nil then obj = DetectedTarget.object tgt = obj:getTypeName() --the name of one of the detected objects end endI hope that will work for you.

It is possible to use lua predicates in mission triggers in order to change a flag value and to use that flag for defining mission scores in the mission goals tab. However, this workaround would not be necessary if it was possible to do that directly in the goals tab. Currently you can define lua predicates in there, but it will be ignored.

That is strange, because in my mission AI Hornets are only refueling when S3-B tankers are available. They dont go for the big KC-135. To be more precisely the Hornets either go for the next waypoint or they are just circling around the waypoint where they are supposed to refuel, if there are only KC-135s available. I hope ED will fix this. Edit: Oh, I should also mention, that refueling a group consisting of 4 AI wingmen is a total nightmare. It takes quite a long time time until they decide which wingman should refuel next. Most of the time they are just swinging around the damn tanker.

I have noticed that AI airplanes with external tanks start with more than 100% fuel. E.g. a hornet with one external tank can have up to about 120% fuel. The problem is that during air-to-air-refueling the AI stops at 100% fuel ignoring their external tank capabilities. For my testings I have used the Unit:getFuel() function, so I could monitor the total fuel percentage of the AI during a whole mission.

I am not talking about shutting his voice off completely. Only unessecary repetitive informations should be at least less frequent. When I locked a bandit up in front of me and jester informs me about it more than one time every few seconds, then I consider that to be unnecessary.

+1 Hope that gets improved, because completly silencing jester is no good solution.

Wow! Coolest easter egg ever!

Just found out how to get out of the Matrix. Instead of swallowing a red pill you have to crash into the rear of a tanker an then you will see this: Ok, I was just kidding

Could we get a less talkative Jester please? It gets a bit distracting, when Jester is frequently bombarding me with obvious informations like "enemy 12 oclock" even though I am locking the bandit for quite a while in front of me. Also Jesters talking during air refueling is distracting for me. Just make his talkings less frequent and I will be fine with it. :)

Good question. I would also like to add the question how Iceman will be like. Will Iceman be able to make some proper maneuvering while the human player can control the Lantirn? Since the AI for autonomous F14s should already exist, it should not be too hard to use it for Iceman.

Why are the options for communicating with my wingman greyed out? I have set radio usage to on in the mission editor, but my wingman is totally useless during combat even when I tell him to engage bandits. The AI is so frustrating in the F14. Edit: I am using easy communication and I am able to speak to the AWACS, but I get no wingman response.

In case nobody mentioned yet: The vally run in Nevada crashes from time to time. Maybe it is because of the checkpoints or something.

The first kind of bug is happening when I cannot click on any of the options in the comms menu. Pressing keys does not work either. Reopening the comms menu does not fix the problem. Instead I have to reload the whole mission to be able again to select the communication options. I have encountered these problems during air refueling missions, but I think it has something to do with the bugged push and talk function in general. The second kind of bug occurs as an error in the log file right after the game has crashed: I believe these crashes occur during BVR fights like in the "Beyond Visual Range" instant mission for the Persian Gulf map. This makes the F-14 unplayable for me currently, because I am not able to finish those mission when the game crashes every time during the interesting phase of the combat. I think before the last OB patch this did not happen. Please fix it asap! :(

Good for you, but this is almost a necro. For a moment I was thinking someone announced the release date here. :D

I have found a way how to change the axis sensitivity by simple button presses. If you guys are interested, then I would write a guide for that.

If you are having no problems with VAICOM PRO, then you do not have to do anything. This guide is just for people who want to create their own voice commands. There are several good tutorials that show how to use key presses in Voice Attack. It is very simple.

Oh, I see what you mean. I was referring to Voice Attack, which is a voice control software. It helps to send commands to the AI while you are using your microphone instead of using keys.

Wait... the RWR is just receiving data from enemy radar. In my case it were ground tanks, that are probably not emitting any radar.

I am not sure which script you are referring to. I never had to use a script for this.

Ok, maybe it was due to the ground radar of the Mirage. However, I am not sure if the radar boundaries of my wingman would be able to spot the spikes, since they were almost in a 90° angle below us when the mission started. Strangely, my wingman reports spikes with a higher priority than bandits. In fact it seems like he can see ground units much easier than enemy aircraft. Maybe the Mk1 Eyeball is not modelled correctly in DCS.

Is the Wake Turbulence already available in the OB just like the damage assessment?