HayMak3r

How long did it take to get the code back? I've been waiting a couple days now, and no response yet. Same thing happened to me with no hardware/software change. Started up DCS literally one day later than the previous playtime, and the sound module was no longer registered. No windows updates or anything. It is crazy how immersive this is.. Not having the ability to feel things definitely impacted my gameplay lol.

What about saving the state of a mission on a dedicated server. For example. I have the Through the Inferno map running. It would be nice to keep the mission "alive" so that if I haven't quite taken out the sam site, the next time I play, I could go finish the job. The dedicated server software allows for "pausing" the mission when no players are connected. Why can't we save that paused state so that if the server needs a reboot for say windows patches, etc. We don't have to worry about starting from scratch?

I have that option turned off, and have a script to start simshaker, and various other items when starting DCS. I get the errors when that is run. If I manually launch simshaker I do not get the errors. Not sure if this is helpful or not, but thought I should share it. Is there any additional logging that I could enable to assist in finding root cause?

Can confirm. mfd's are WAY harder to read after the 2.7 patch. I also upgraded my pc, which forced a format, reinstall of windows, and DCS. This happened pre upgrade with 2.7, and also after with a brand new install. It is very frustrating again. It seems like it has been reverted back to the issues the mfd's had when the viper first released or so.

Trying to track this down. I never had this issue prior to reformatting and upgrading my machine last week. Now I get this if I have simshaker set to start with windows. I uninstalled, and reinstalled the beta, and the beta does this too? Trying to go through this huge thread to find others with the issue has been painstakingly difficult. Has there been an official resolution to this?

Just checking to make sure that these two items are the same?

Thanks for the track. just came to check on this, as I didn't see it in the patch notes for today. This is a pretty huge deal. We can't accurately predict when we will make it to a given stpt, which makes it hard to make push times when flying. I see it in both SP and MP, so this should be easily reproducible. even without a trk file.

Came on to here to look to see if this was posted. My flight including myself all noticed this last night. We no longer have the time to waypoint post yesterday's patch.

What was it? My comms menu just stopped working, and I am pretty sure I didn't touch anything.

Thanks BigNewy. Culling is enabled in my scenario, and understand that there are things like seeing certain lights etc in only one eye. As for the tgp, or really any video viewing, so now also the mavs, the resolution is not great. I use the rift s, and it is VERY hard to find a target. If there is smoke down, then forget it. We have to use manual gain control to even have a remote chance of finding anything. Can you provide your settings to see if there are differences there potentially? With the hornet, or a-10 I never had an issue with the tgp. but the viper is just not good. Of course it does help if you zoom in on the mfd, but should that really be neccessary? I am trying not to neccessarily complain, but please understand that it is not ideal right now in the viper.

tgp is not good in vr.. culling is causing the lighting in your right eye. I believe there is already a thread opened for the tgp issues. Hopefully ED fixes the imaging issues, as well as the other tgp issues soon.

going back to tgp and doing cursor zero seems to resolve this, though I would think that isn't by design?

The sound IS there and is a bug. I can play in SP, taking off from guadata, and every so often, when I take off, it's almost as if the sound is something along the lines of an overspeed of the gear? and it sticks with you until you restart the mission. You go in to afterburner, and it goes away, drop out of AB, and it comes back. Super loud and annoying. And it is being reproduced in my bass shakers too. Big Newy there IS a bug here somewhere. I am not sure why it's not getting picked up in the track file.

If the lock is supposed to stay when the distance changes, then this is a bug. I can repro this every single time I have a lock in single player. I have not tested in MP. I lock a target while the distance is at 80nm. it changes to 40nm, and I have to re-lock the target. Everytime..

I searched through the thread, but it IS 280 pages.. When in the viper. The engine sound doesn't seem to sound right to me? I was just curious if it is supposed to have a "thumping" type sound? Almost like it is piston driven somehow. Do I just need to tune airborne piston engine rumble setting more? Or is there something else I should do? It just doesn't seem to match the sound or feel that I would expect. Outside of that, adding this to my setup has been great!! I am using an aura bass shacker for now in mono mode. I am using the sound blaster x G1 for the sound output going to an 80 watt 2 channel amp. Cheers!