TheBamse

@SmilingBandit The gateway is already in the game and has been there for a quite long time, just place an E-3 or similar AWACS in the mission and you're golden. The specific case of non-friendly air not being shown is not due to a gateway not existing in the mission tho as per the info from Snoopy.

c0ff: Thanks for clarifying that the list doesn't show ICMP Echo rtt's but an amalgamation of the above and application processing. But I do have to join in the choir here, even after November 2019. Pings listed in the server list is at best a guide to show if the server is on the same continent as you or not and will fluctuate wildly, especially on first entering the server list after starting the game, then there's often a 100-300ms addition until you refresh the list again and then one might start seeing pings closer to whats actually going on. Direct connect or just double clicking your servers you've marked as you favorites that "you know are ok" is how the list is used on this end :)

+1!

well, we got flashbangs in the cockpit with the pulled 2.5.6 so I'm guessing you are getting some progress on this item atleast? ;)

I rent a "root server" from hetzner.de. It has been working amazingly well for about five years now, even pre-dedicated DCS server and even before I started playing DCS and found an amazing group of ppl to play with. If it's worth the price? Nah, you'd be better off buying a server of your own (if you got internet that's good/stable enough for your needs that is), it'll be cheaper in the end. If you're looking for a more SaaS-oriented hosting platform I have zero input, not my thing :)

Not sure the argument to have the mission maker shell out "extra" money even grazes near my own way of thinking. Mission makers are the ones actually creating content for the game no matter if it's MP or SP. Are those the ppl that you want to put all the weight on (I know it's voluntary to make missions but many companies do take the route of making it easier to make missions, not harder), now also including the financial part? I dunno man ... :/

Couldn't agree more with the above posts. What a strange argument made by ED through NineLine. I just cannot wrap my head around the presented reasoning. To me it just seems based in some kind of inhouse ED-mentality how things should work or be, not really shared by non-partnered content producers. You do you ED, but for me the reasons not to pre-order stuff anymore just becomes clearer and clearer each weird announcement.

There is an updated version for 2.5, or rather I should say using that build works great on my end. https://forums.eagle.ru/showthread.php?t=257887

It's all in where you look, like here for example: https://forums.eagle.ru/showpost.php?p=4129745&postcount=178

Yes, the current workaround as per post #914 is to delete the file DCS doesn't like from the mod package before applying it: bazar\shaders\deferred\shadows.hlsl Do that or wait until someone publishes a fixed shadows.hlsl and/or the official download is updated :)

!

Just fyi; video is set to private so even clicking the link doesn't show the video :)

I can confirm on my end too with 2.5.5.40603

Nice, will try it out tonight. Thanks for all the work you spend on this!

That's on the lower half on the Stores-page was it not?

Until ED allows us to via DCS's own options run it as a system service you have the option to add it manually as one using the sc-command or use something like FireDaemon. I haven't tested it myself but since it's a rather straight forward command line execution starting a DS I can't see any glaringly obvious reasons it shouldn't work :)

Yep! The RECCE event mark button binding is used for this, it acts like a on/off-switch after the twist-knob is set to whatever brightness you like.

My pleasure, I'll check it out the coming weekend. Thanks again!

Hi! Happy user for a good couple of months here :) Recently after update:ing from 0.9.0 to 0.9.1 (and updated OB to 2.5.5.38140 at the same time (and running SRS Server version: 1.6.4.0 since it was released) I have gotten a weird behavior; All stations connect just fine to SRS but all transmit for 0.5s then stop, then start then stop and so on. Listening in on client SRS it sounds like someone is hitting the SRS-PTT over and over and over without saying anything and this is also visible if I look at the server's SRS Client list. They transmit on and off making the list look a bit like an xmas tree :) Downgrading to 0.9.0 does not fix the issue. Has anyone seen something like this? I've enabling debug logging and see no errors and all stations generate text for G-TTS just fine according to the logs.

The regular A/B/C models of JSOW that we have, or will have, in-game does not have a rocket boost. There is a JSOW-ER but that's not something we have the pleasure of getting our dirty mittens on.

Undo/redo Select units by drag-box. Polygon zones Layers/grouping of units Unification of waypoint options between unit types (let all unit types switch waypoints etc) Freeform callsigns and numbering (let us type in any squad/unit number and callsign and tts it since we can't group aircraft in MP due to scripting issues) Tankers, options for: unlimited fuel, speed adaptation and announcing upcoming turns Wind direction fix Map/briefing drawing Mission planner for MP Change coalitions after mission creation Neutral coalition 3D-editor :)

Yep! Can confirm. Downloaded the new version as soon as I say the bot notice on MOOSE discord. Works 10/10 with todays' MOOSE dev.! :)

Just for knowledge after having a discussion with Hardcard on Discord: I do have one issue and it's with the latest OB as of this posts date, latest moose dev. along with SWAPR 1.2 set to MP (with hooks file placed in the hooks dir). As soon as SWAPR loads I get this error in the logs: 2:16:36 PM.614 ERROR DCS Mission script error: : [string "c:\Users\admin\Google Drive\05. Lynx\Missions\Scripts\SWAPR\SWAPR_PnP_Hybrid_v1_2.lua"]:720: attempt to index local 'ClosestAirbase' (a nil value) Moose loads 1 sec after mission start, swapr 15 seconds in. The error seems to depend on a change in Moose dev. (if I understood correctly) and Hardcard has given me a temporary workaround by using a slightly older version on Moose (the one included in the SWAPR download package) and that is working a-ok from my testing!

Same here! No issues with latest OB and latest shader package. No other shader mods but a small pile of general texture and other gfx, sound and functional mods.