epoch

Bearings ... reciprocals ... fuel weight ... time ... coordinates. Get used to doing maths :smartass: You're a virtual pilot now :pilotfly: Seriously .. there's no avoiding having to do calculations on the fly (literally). It's part and parcel of flying.

This perhaps ...

Screenshots look amazing! Really looking forward to this module. Not sure if this has been asked earlier in the thread, but how will duplication of axes between front and rear seat work? For example, I'll map my roll/pitch to my Hog joystick for use when flying. If I'm in the back I'll want to use the same joystick for that RIO stick (assuming it's an axis?). How will that work? Current controls behaviour would delete the previous assignment.

Definite issue on some EHSD pages, but is infrequent and unpredictable. Shaders etc cleared but it still occurs. You can see the flickering on the clip below. Also notice how the sea turns to jelly. Apologies for the quality ... no idea why Youtube didn't render it in HD.

Tracks?

English Electric or P-38? :music_whistling: Good luck with whatever you're planning on developing!

Experiencing same.

The Harrier is by far my favourite module. It's great fun, pretty easy to learn it's systems, and not that difficult to fly. Even vertical carrier landings isn't too difficult, once you get the hang of it. But for sure there's some issues that have been outstanding for quite some time, and little evidence that any attention is being paid to them (though apparently you have to be on Facebook to keep up to date with 'development'). If you can cope with the negatives I'd say get the Harrier.

There should be no need to forward ports locally. Your computer is establishing the connection to the 'master server' and it does this on a random port. The remote end (i.e. the server) has the "known" ports, such as 443 for login authentication and 10308 for game server. If you want to see what your computer is doing, you could download a neat little utility called CurrPorts. It will show you which connections your computer is making, and which process (e.g. dcs.exe) is making them. That might help with your troubleshooting.

Hi Yeah, we're aware of the configuration options. We have A2G hard SAM set to 2, so clearly there's something not quite right here! And other A2G hard spawns also ignore the setting. I've never seen less than 3 SAM batteries despite setting it to 2. Still great fun though. :thumbsup: Edit: could this be the culprit? for i=1, [b][u]25[/u][/b] do A2G_SAM:SpawnInZone( AG2, true ) end I see the 25 for AG1 and AG2 only (though we've never seen AG1 spawn, ever).

What's with "SAM-CON 2019"? We've seen this a few times. We spawn an A2G hard mission and we get one that's quite challenging to say the least. Seems there's a SAM convention going on in Iran. I counted (I think) 6 x S-300, 6 x SA-2, 6 x SA-3 along with similar numbers of Osa, Shilka and Tunguska. From the layout it looks like a copy/paste error. It's certainly a challenge! But is it intentional?

This used to happen to me. Culprit was my antivirus software (BitDefender). I turned off the 'Scan SSL' feature and the server list started working.

I think you need to place a ground unit at the FARP transmitting on FM. I did ask about this last year, and Maverick said he'd put it on his to do list, but perhaps hasn't got round to implementing this yet.

Love the mission - thanks for creating! Being able to spawn in units is a great addition. But on that .. I spawned a couple of F-14s (for some "ambience") whilst my buddies and I were getting our Harriers ready on the Tarawa. The F-14s proceeded to descend and attempt a landing on the Tarawa, ploughing through the four Harriers which were just about ready to depart. Much carnage ensued. Very funny to watch, but any idea what happened here? Tried the same later with an empty tramline on the Tarawa and the F-14s landed successfully (amazing!) then taxied back through the island. Why would they even attempt to land on the LHA? Anyway .. really enjoying the mission.

Can concur with OP. This does happen on occasions but I'm unsure what triggers the issue. 99% of the time my Mav Gs work as expected.

Not sure if this has been acknowledged (couldn't find a report) .. Player A gets tracked/launched on by, for example, S-300. He gets the RWR alarms Player B also hears the RWR alarms, despite being nowhere near (in my case, over 100 miles away). Player A was in a Hornet, but same experience when he was in a Harrier. Player B (me) was in a Harrier. Unsure if this is Harrier specific or DCS World. Repeatable issue, and presumably unintentional.

I've tried checking/unchecking the 'special' box yeah. That's what the ["MPCD_EXPORT"] settings is in the options.lua I pasted above. What I did to get it permanent was follow the thread I linked to in my original post.

Already been there. Not enabled. This is my .lua _ = function(p) return p; end; name = _('1 Screen'); Description = 'One monitor configuration' Viewports = { Center = { x = 0; y = 0; width = screen.width; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect; } } GU_MAIN_VIEWPORT = Viewports.Center Yes, that's the problem. As far as I can tell I'm not exporting them. From my options.lua: ["AV8BNA"] = { ["CPLocalList"] = "default", ["INS_Alignment"] = 0, ["INS_GYROHasNAV"] = false, ["MPCD_EXPORT"] = false, },

Anyone able to help me with this one? It's driving me nuts!

More like jam I reckon. Or perhaps custard.

:thumbup: This! ^^^

Much appreciated, thank you. :thumbup:

How do you do this, please?

=DECOY= this is an old bug, from when the module released. It's been reported several times and yet still no resolution. It requires no other steps to reproduce other than to try to use the feature. Whilst your advice is appreciated, understandably there's some frustration from Razbam's customers given the age and severity of this particular bug.

Not new. Longstanding issues.