Shogun0

Is this even necessary now? With the WMR for SteamVR Beta version, you can uncomment the highlighted line below out: { “driver_Holographic” : { // Increase back buffer size so that larger superscale values do not get a resolution reduction “renderTargetScale” : 2.0 }, “driver_Holographic_Experimental” : { // “motionReprojectionMode” : “auto”, @Willie, here is a good site that has a bunch of optimization info for DCS and VR. https://vr4dcs.com/

So I got my Reverb this week. I would akin the SDE in it similar to using a regular monitor. If you stare really hard at your screen, you can maybe pick on individual pixels but you have to absolutely be looking for them. I had the CV1 and the Odyssey, and it is night and day difference. The Reverb is super clear.

Nah, keep it and let us know if it's everything as advertised :)

I was tempted to pre-order this but with the month of no updates, I'm back on the skeptical train.

Still crashing... attached log files again if anyone sees anything that sticks out.. dcs.log-20180704-150948.zip

TACAN callsign were broken in the last patch unfortunately.

Hey guys- Having an issue with our DCS server crashing. I took a look at the crash files and seems to reference this AyncNet.dll quite a bit: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\AsyncNet.dll # C0000005 ACCESS_VIOLATION at 191B7060 00:00000000 00000000 00000000 0000:00000000 191B7060 8BBEDFA0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\AsyncNet.dll 191B770C 8BBEDFE0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\AsyncNet.dll 1917FB30 8BBEE140 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\AsyncNet.dll 1918721C 8BBFE1E0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\AsyncNet.dll 19186FD4 8BBFE2C0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\AsyncNet.dll 191868BE 8BBFE340 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\AsyncNet.dll 1918203D 8BBFFC00 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\AsyncNet.dll 0BEFEE2B 8BBFFC40 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\edCore.dll ?clear@StringsCacheWithIndices@ed@@QEAAXXZ()+C9B 3DADC1AE 8BBFFC70 0000:00000000 C:\Windows\System32\ucrtbase.dll _o_strcat_s()+5E 3F363034 8BBFFCA0 0000:00000000 C:\Windows\System32\KERNEL32.DLL BaseThreadInitThunk()+14 40971431 8BBFFCF0 0000:00000000 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 I went ahead and followed the guide to do a Cleanup and then a Repair. I have seen this DLL referenced in other crash reports- just wanted to provide more data and see if anything obvious stuck out. Thanks! dcs.log-20180627-024858.zip dcs.log-20180627-003512.zip dcs.log-20180627-003058.zip

Thanks for the reply! This is the thread about the TACAN issue folks have been seeing, with the workaround: https://forums.eagle.ru/showthread.php?t=210937

Just wanted to confirm, all TACAN callsigns have disappeared and the time to go is gone as well.

Good! Couple questions! First caveat, I watched most of the video, but may have missed some things. Also, I am not at my DCS PC. So I haven't been able to download the miz file yet. 1) Right now, TACAN has a pretty well known issue. For some reason on the carrier, it will die after an amount of time. The workaround we have is to add additional TACAN activation triggers along the pre-plotted route (headwind). Is there a way to have these dynamic waypoints all include the TACAN triggers. Is it somewhere in the script we can add the TACAN triggers to these as well? 2) Is there a way to make a message to all regarding carrier heading? If the heading changes, we would want to know not only is it turning, but what the new BRC is going to be. I have been learning quite a bit of MOOSE, but haven't had a chance to delve too much into MIST. Thanks for the work and the great video. Appreciate it.

Yup. The workaround that we have been using is to set new waypoints along your carrier's path with triggers to reactivate the TACAN along the way. I have a WP setup at every hour for 6 hours, until the mission restart trigger kicks in for our 24/7 server.

Hey thanks for the reply! Hope you don't mind if I pick your brain for a few. How did you come up with those numbers for bandwidth? I don't want to just blindly copy what you guys are doing to help smooth out things (we are ~50-60 folks online at a time now when we have our flight nights), should we consider some bandwidth tests for down/up on the server itself and how we should have clients configured? Not a network guy at all, so I'm a little dense. Apologies :)

Do you guys still recommend using the autoexec file for all clients connecting to your server? As our group grows, we are getting a large number of players on our flight nights and are looking for anyway to help some of the lag/disconnect issues. Still relevant in 2.5? Thanks!

Having an issue in Multiplayer. When we first load the mission, the tankers TACAN all list the 3-digit callsigns we have assigned in the mission editor. After awhile though (15-20 mins), these callsigns disappear and are replaced with either a blank name, a single . , or a group of three like this: ... Kind of weird. I have seen in a few videos that other folks are seeing this too, curious if we are doing something wrong? An example of when it goes FUBAR:

Anyone else seeing this? We are currently experiencing this in our Multiplayer server after the mission has been running for awhile. We have the TACAN set to 40X, so I don't think it is related to the default 1X. We end up having to have to do a reset on the mission every few hours once the TACAN magically stops working.