funkyfranky

I have to sincerely apologize for my rather harsh words above! That was the heat of the moment, I guess. I fiddled around with some audio settings in the Oculus app and was able to get back to my normal "workflow" quite easily. In fact, I begin to like the new feature (without quotation marks intentionally :)). But making it optional seems to be a good idea for people who have more problems with their additional hardware.

Thanks, HiJack! OvGME version is much appreciated :thumbup: And thanks to Mustang, of course!

Wonder if HB will hide an Easter egg to make Jester do "the finger" :D

http://cam.em-key.de/2018/05/03/airbus-a320/ :D:thumbup:

Super infos, die man sonst kaum bekommt. Danke!

You can find every function of RAT here https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/Rat.html However, these are really all functions, i.e. also the ones which are used internally in the code. But the internal functions usually (but not always :music_whistling:) start with an underscore. I'll try to find it :)

Let me know how it goes. And if it still does not work, attach the miz file so I can have a look :)

Or conveniently RAT:AddFriendlyAirportsToDepartures() RAT:AddFriendlyAirportsToDestinations() would at all friendly airports for either departure or destination.

Here is another approach. Actually also heavily based on Ciribob's great script but using MOOSE. https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/Range.html

+1. Good documentation and great support by the developer Hollywood as well!

Is there a way to get the firing range of units (in particular artillery) via scripting, i.e. can these be found in any of the descriptors? I'd like to check if a target, which has been assigned to an arty unit is within range. Because if not, the task fire at point will not be executed. I know where to find the min/max range values in the lua files but I'd like to avoid building my own data base for all arty units. Or alternatively, is there any other way to check that the fire at point task cannot be executed by the arty unit? At the moment I check after a certain time interval if the event shot occurred for the unit. But it would be nice not to wait ~5 min before it is clear that the target is out of range.

Hi pmiceli, good that you attached the miz file straight away. Lua is case sensitive - and in your RAT lua file you have --RAT EMS local RAT1=RAT:new("RAT1") RAT1:spawn(3) --B747 local B747=RAT:new("B747") B747:spawn(3) You need to capitalize the ":New" and ":Spawn" commands, i.e. --RAT EMS local RAT1=RAT:[b]N[/b]ew("RAT1") RAT1:[b]S[/b]pawn(3) --B747 local B747=RAT:[b]N[/b]ew("B747") B747:[b]S[/b]pawn(3) Then it should work :) If not, let me know...

That vid is exactly one year old. But I guess you also knew this already.

Just did a quick test. No issue like describe here either. Any special setting to reproduce?

Frankly, this is not a even a "feature" in quotation marks for me. This is a pain in the :censored: No explanation why, no info that this was changed... First thing you think is that something on your hardware side is not okay. You spend quite some time to figure out what it is until you realize that it was changed in the game suddenly. Bottom line, things like this should be mentioned in the change log. That's what it's there for - old story, I know. Probably many hours of customer time in total wasted because ED could not be bothered to take one minute to write this into the log. Actually, I still don't know what is going on exactly. How is the audio output handled now in comparison to the previous DCS version where my default audio playback device was used?

@Raku, es liest sich lustig aber ich kann mir gut vorstellen, dass es als Betroffener echt nervig ist. Gerade, wenn man dann noch bei der Arbeit Stress hat und seinen Schlaf braucht. Wenn der ganze Umzug etc über die Bühne gegangen ist, kannst Du aber hoffentlich auch drüber schmunzeln.

Hi maverick, code looks fine and should work. Can you check the name of the template group of the F-16 and that it is late activated. If it does not work, attach the mission file please. Then I have a look :)

Already posted in the other thread. But I´'d also like to state here that this new "feature" is very annoying.

Same problem here. I switch my default sound device via the normal windows GUI. However, since DCS 2.5.1 changing the default playback device has no impact any more as soon as DCS has been loaded. Setting the default playback device only works now, if one sets it before starting DCS.

Is is?! Well done, guys :D

Oh, that is fixed?! Nice :beer:

Heatblur - Nothing On Earth Comes Close

Cool, thanks for the update!

I perfectly understand that you don't understand what I'm saying.

I was referring to your false and out of place accusation against Heatblur. My statement still stands (and what you are citing has no relevance to my post). But judging from what you answered, I don't expect there is much I can do to prevent you from demanding explicit dates just to complain in case they were not met (or even before). The sad thing is that you might be spoiling the party for the rest of us...