markom

Ohhhhh this is nice trickery with the scripting I didn't think of. NICE!

I do believe there's a command for AI to refuel. I never made it work reliably, so can't help you much there. Regarding your orbit looking like a circle -- make sure it's far from WP1 - 10-20nm.

It's #1 most annoying alert in hornet :-). I especially hate it when it starts beeping while I'm trying to land. Like... I KNOW, I GET THE IDEA DAMNIT. STOP IT. I also can't seem to find a reasonable way to silence it, but that just may be me.

Are F/A-18s human or AI? One approach you can do is: - Launch tanker, and make it orbit a WP - Set the limit of orbit for a flag being set - Set the flag to true when refueling is done. - Tanker RTBs after WP No idea how to program AI to refuel. I never managed to do that.

Make sure to turn it on. It's not on by default in hot start :-).

Oh yeah, totally! It may make sense to outline that in a sentence or two. In hindsight, that's precisely what "focus on immersion and gameplay" means, but still it makes sense letting folks know.

Isn't that what WW2 pack is for?

Those tend to be very helpful when asking other folks for assistance...

Let me start by saying that I quite enjoy the campaign. I love the "short format" of the missions so far. I do have a question/confusion about the mission success criteria. I will ask below because it contains spoilers for the first two missions.

I also tried a few times after that and it did not happen. DCS does what DCS does

I am seeing WP6 because I need glasses and am forgetful. Yes, it seems to be off-by-one, but in the other direction :-).

I didn't say it's an insolvable problem, just that it's a thing that exists as a challenge in even the most trivial code While I am by no measure a Lua expert, quick binging for "Lua mutex" yielded some promising results...

Note that multitasking is not really the same as multithreading. Same way as multithreading is not automatically concurrent, or parallel, or asynchronous, or synchronous. These are all possibilities that having multiple threads open up, but it's up to the implementation to do one, or multiple of these. I spent 0 time trying to figure out what kind of implementation DCS went with, and what it means for user scripts. However, it is entirely plausible (and also implausible) that each user-supplied script may get scheduled on a different thread than another user-supplied script. It could be that all user scripts get scheduled on the same core. These are the levels of details only ED can answer at the moment. Note though, that programming for concurrent execution is complex. For example, imagine a simple data structure that has some variables and methods (aka: an object): type person struct { name string } func (p *person) GetName() string { return p.name } func (p *person) SetName(n string) { p.name = n } This is Go definition of a structure defining person with one variable, one "setter" and one "getter" method. Now, this looks like a perfectly fine code. However, this code is rather problematic in multithreaded environment. What happens when two threads call GetName and SetName at the same time? This same class of problems will rear its ugly head if parallelized scripting is implemented in DCS... It's arguably a lot worse than scripts being bottlenecks :-).

While I have no desire to diminish your entertainment - that camp was kind of supposed to be somewhat difficult to spot, that's part of the charm! Same way the next target may be unless you use a technological means to make it dead easy :-). The provided map gives you a solid clue where to look for it. On the first flight of M01, I needed to make several circles before I saw the camp and not a village. It was right where the map suggested it would be :-).

MT is a preview feature in a beta, in a separate executable file. I am not quite sure how much more ED could have indicated what to actually expect in terms of its completeness and buginess... While they figure this out, you may just use ST, as we all have until Friday.

I missed the target by at least a mile, yet the follow-up ground strike was a success.

Right after takeoff, a few miles straight out, Mirages appear frozen in the air. They rejoin sometime between briefed rendezvous WP and the next one, but this looks weird. This happened on all replays of the mission.

Provided docs list WP6 as the target WP, but kneeboard lists WP5.

I just tried to fly M02, and as soon as we started taxiing, F/A-18s in front of F-15s (talon?) crashed into each other and mission was essentially stuck.

You just dated yourself... and probably I did, too since I totally remember that

From what I understand, it will among other things ensure shader files and caches are recreated. It has been a fix for various other graphical glitches. So... it could be.

Yeah, was I knew, but was looking for a slightly different behavior, which... ... this may be close-enough to to be useful! Thanks!

Most aircraft I've flown (either virtually or irl) have autopilot function that sets the HDG bug on HSI to the current a/c heading. Is there such a thing in Hornet? I've tried what I believed were the obvious clicks and holds, but couldn't find it.

For everyone else, while ED fixes the underlying issue, we could use a workaround that wonderful folks have already figured out: Nah, we good, man. You were very clear this was a preview... in a beta (!!!). We expected things to break. It's super-exciting to even glimpse how much better your product will be once you iron out the kinks. Keep up the good work!

Of course - that's the beauty of a feature rollout behind an optional flag. We can always fall back to the previous behavior easily, but... hopes were high, since on my rig I can't have all the cool graphics and stuff in ST, but MT seems to be able to do it. I am truly excited about it! Keep up the good work! As a side note, and I don't know if I should report it or not (it *could* be related, or a different bug) - in F/A-18 exported DFD views are really blurry/bright/yellow. This could be related to them not actually being refreshed, but could be something else totally.