Mustang

Getting a 'Timeout was reached' message while trying to update the openbeta, maybe they're working on something :music_whistling: (anyone else seeing this timeout message or just me?)

Yeah I was just being a bit salty cause I wanted my OB update :D It is an impressive list like you say.

Yeah I have this problem too and I think it's been reported elsewhere in the forum a little while ago. Found it https://forums.eagle.ru/showthread.php?t=211856

104th_Mustang AV-8B, F-5E3 or MiG-21BIS.

Was anyone else utterly stoked at the size of the changelog today only to slowly realize that it was everything the open beta already had lol

I have the biggest OCD when it comes to PC's just ask any of my squadmates :D

That's a negative, already tried it but it seems something has been pulled out of the graphics engine that allows the Raymarching cloud effects, bit of a shame really.

In 104th server, but with further investigations it seems the AIM-120 is at fault the most.

It doesn't matter what angle or distance the missiles explode near the airframe, the result seems to be the same everytime.

Not sure if this has been mentioned elsewhere in the bugs section but has anyone else found the F-5 damage model to be exceptionally resilient to missile hits? My experience has been during multiplayer fighting against other clients, it takes at least 2 missiles (sometimes 3) to finish off this tiny jet and if you hit the F-5 with only 1 missile he will always fly away with only a little bit of smoke trailing behind him almost unaffected.

It sounds like you need to use a custom autoexec.cfg file to allow the server to open up the upstream/downstream speeds so it can cope better with traffic and mission demands, download this file: http://www.mediafire.com/file/azm56gshu5fja97/autoexec_for_server.rar/file extract the autoexec.cfg into your servers Config folder (example Users\<name>\Saved Games\DCS.openbeta\Config) and see how it goes.

They're the same textures with the only difference being the MIPMAPs use an alternative method that makes them look alot more detailed and less 'mushy' from a distance. see the links below :)

PM sent.

Yes always it helps ALOT especially when the client counts go into the high numbers and when there's alot going on.

104th server now @2.5.2.18736.400.

It's an MP bug not only with the Persian Gulf map but also with the Caucasus map, hopefully ED is aware of this and can fix it soon.

Yep it was not quite what I was expecting, it was a great time :)

Yes IC will block it by default, but if server allows textures (require pure textures = no) it will work just fine. You can check via the info displayed in the bottom right corner as highlighted in this screen capture of the MP lobby

No sorry I don't know, maybe they'll see this thread and use these textures who knows, or they might make their own fixes (or maybe none at all!)

(P.S I notice that Imgur tends to ruin the image quality somewhat when converting the image to .jpg, the original pics are much sharper with less compression)

Just received the ED newsletter, straight away the "This week we released an DCS 2.5.5 Update 4" typo caught my eye and made me think wtf for a sec :D

You can edit the graphics.lua quite safely without busting IC, but as you say it would be easier to make the autoexec.cfg file.

Yeah it's an incredibly annoying bug one that I hope get fixed soon, another bug thread https://forums.eagle.ru/showthread.php?p=3527612#post3527612

The changes you manually made to your terrain.cfg.lua should be good so you won't need to re-download (noise1 and noise2 parameters)

Thanks for the heads up Holton181 i'll update the mod packages to include the newer terrain.cfg.lua file :)