Camble

I honestly wouldn't mind that as a temporary measure, a step in the right direction. But still, this isn't just a VR problem. The fact that the viewpoint doesn't move with head movement is one problem. The other is the stereography, but I'd settle for mirrors that don't spaz out when I move my head. The Mi-24 is perfect extreme example. There are plenty games with working mirrors, both flat and VR, without a noticeable performance hit. Current DCS mirrors tank performance, and I'm pretty sure it's because they're implemented using a 20 year old approach. Have you ever played Lock-On? Real-time rendering has come a LONG way since then. Convincing reflections can have a negligible performance hit. I don't really think there is a "best working module", because they are ALL reliant on the current mirror implementation. I also feel that making excuses for the current implementation does nothing to progress sorely needed improvements to the engine.

On re-reading your post and my response, I see what you mean. It's true, that VR would require stereographic rendering for the mirror. This doesn't necessarily have to cripple performance if done correctly. The biggest problem with the current implementation is that the mirrors act like a stencil over a single viewport rendered in reverse. So when you move your head, in 2D or VR, the image in all mirrors moves as one, which is completely immersion breaking.

The current implementation is more of a performance hit than a more modern implementation could be. And nobody is expecting 3D mirrors, because mirrors don't work like that. See the video I linked above for an example of the problem.

It would be nice if someone from ED at least acknowledged this is an issue.

Found and resolved an issue with detecting when DCS was running, if you run DCS as an administrator. Not sure how many people this will affect, but next update fixes this. Probably won't bump this thread on every single new version, just if it feels appropriate. Livery Link automatically updates anyway.

Bump again. New Fulcrum announced but still having to put up with janky mirrors.

Must just be a typo. I've never encountered that issue until now, but that's just the way it is when working with manual submissions. A future version will have to infer the aircraft type by the file's contents (so we can make use of other hosts like Google drive), but for now we're reliant on which category people upload their liveries to!

I'll check it out. Do you have the user files URL? Was it this?

I'd like to introduce Livery Link, a desktop application for managing custom liveries. I've been working on this for a few months now and although it's still incomplete, there are a few people using it and I think it's in a state where I'm happy to share with the wider community. The primary function is to make it trivial to install liveries (see the video below). In addition to this, it can also automatically share liveries with other people. So far, I loved building this, I really hope you enjoy it! For those interest in the server, I've created a Server Functionality Poll to get a feel for the kind of features people would like to see added. Download Visit https://github.com/Camble/LiveryLink for more information click the download button for the latest version. User Files link: https://www.digitalcombatsimulator.com/en/files/3339586/ See it in use: Key Features Paste in a User Files URL to automatically install a livery The Livery Browser displays your installed liveries with nice thumbnails Plenty of options in case you don't like a specific feature Automatically share and download liveries (with other users of Livery Link) Installation No installation required, extract anywhere you like and run. FAQs Q. How does Livery Sharing work? A. In order to share liveries to other players, they must also have Livery Link, and the server you are flying on must be running Livery Link Server. Q. How do I enable livery sharing? A. Simply install liveries with Livery Link, and use those liveries on a Livery Link enabled server. Q. How do I send liveries to people? A. If you're sporting a livery that was installed with Livery Link, it will be shared automatically as soon as you take off. Q. How do I receive other people's liveries? A. If connected to a Livery Link server and a player shares a custom livery, Livery Link will download and install it automatically. Q. What if I don't want to share liveries? A. This feature can be disabled, or tweaked to your liking.

I figured as much. That's most unfortunate.

I know this is a long shot, and I've seen plenty posts asking how to set liveries on a Unit or group, but I'm looking for a way to get the livery name/id of a Unit or player Slot. I'm 99% sure the answer is going to be "it's not possible", but if the data is available I'd like to know. Thanks!

Bump. This doesn't just affect VR.

Not exactly untouched, because work had to be done to get them working in MT. So why not address the issues then instead of bringing over an old implementation that isn't relevant for the current state of the engine? Fine if you never move your head, but almost everyone has 6DOF head tracking or VR these days. These mirrors are completely wrong and immersion breaking.

This is one of my biggest gripes with DCS at the moment, but it's not just a VR issue. It's just more apparent in VR and completely disorienting and immersion-breaking. I'd say this is less about depth perception and more about the way mirrors are implemented in DCS. I presume this is because because originally, the pilot's head was stationary, but you can witness a similar perspective issue with the mirrors in 2D by moving the pilot's head. And as others have said already, it's not impossible to implement without a performance impact. The existing mirrors are a throwback from Lock-On and desperately need replaced.

I mentioned this in Discord, so I'll repeat it here. Why completely block access via Steam? Just prevent people from using both instances on the same account, concurrently.

Is this ever going to be addressed? 5.1 is old hat https://www.lua.org/versions.html

Seems to be fixed in both ST and MT!

Something I've discovered that might be helpful. I've experienced this issue on several driver versions (even prior to 22.12.1) and I seem to be able to avoid the crash if I follow these steps: Open the mission editor Create a blank mission Disable "show models" on the bottom bar Open the offending mission I thought just disabling "show models" was enough, but if I don't start a blank mission first, I get the same colourful show then crash. Also, the instant I re-enable "show models", DCS will hang/freeze but not necessarily crash. It does actually recover.

Agreed that point lights should render much more distant than meshes. Our eyes are sensitive to small distant lights in the dark, it doesn't feel natural for runway lights to appear out of nowhere. Maybe a separate setting for lights?

I'm not sure this is true. Results may vary between games, but it basically just expands how much of the frame buffer the CPU can access at once.

Instantaneous selection, copy & paste. If anyone is interested in testing an early version, give me a shout.

Progress...

For anyone interested, I decided to take this on and implement it myself. It's too frustrating to select dozens of groups one at a time only to mis-click and deselect everything. I'll make this available when as soon as I can.

Important, especially as people spamming the join button actually impacts server performance for those currently playing.

Think I've found the cause of the problem. The mission I'm running has a timed event to reload after 4 hours, and calls the mission by name. The mission was renamed months ago. I cleared the logs and ran the server without any resume setting, to let it run through and generate some clean logs. This revealed an error trying to reload the mission. Changing the event to END MISSION instead of reload got rid of the error and the server seems quite happy to jump to the next file now. Changing the mission duration to 10 seconds allowed me to test a rotation of mission files very quickly. Still doesn't explain why it was working for 2 months without a problem, but hopefully this will help someone with a similar issue. @Eld0r, thank you very much for your input!