RuskyV

Agree with you here, if I’m not correct I thought that ED were holding 3rd party developers to the very high stand which themselves to a degree completely ignored. I understand the concept of early access but when all ED seem to do is release early access modules It makes you start to think twice about who’s modules are worth purchasing at the end of the day... Interesting point though:smilewink:

Hi Cintra, I noticed that you said you have reinstalled your OS recently, did you turn off the windows game mode? as this one can cause you issues.

Did you disable or completely remove the comment from the autoexe.cfg file before trying this option? I would personally remove the comment boot DCS then, exit out and then set the option I described. You could also clear out the metashader2 and fxo file from your saved games folder before rebooting DCS. Might help.

Actually on the "VR objects not rendered in one eye" bug I have found that if you go into D:\Simulation Games\Program Files\Eagle Dynamics\DCS World OpenBeta\Config\Graphics.lua And scroll all the way to the bottom you can set the below option --in stereo and hmd mode you can try to use single parser for both eyes , by default is false , comment to enable it or set to true stereo_mode_use_shared_parser = true This option actually works for me as apposed to the one that everyone is entering into the Autoexec.cfg in the saved games config folder, in fact if you have this set there then you are going to want to delete this first before setting the above. This cured my cloud issues.. Hope this helps

you can change this in the special options menu for the airframe you fly.

Go to your save games folder and delete all the track files from the folder, these can get fairly large and if you have a lot of them you will be surprised how much space these take up. Got to: C:\Users\YOURNAME\Saved Games\DCS.openbeta\Tracks you can right click this folder and check the properties if you are curious about how bit this file is before deleting the contents!!

Wasn't this a thing when Blackshark was released way back? I could have sworn there was a way of listening to music through the radio?

Just another thought, are you using any frame buffering? I know the nvidia cards have an option in the profile that can allow up to 4 bufferd frames. Not sure if you are running this setting but i know that this can also cause a delay in input.

Well that's got me completely foxed as to what it could be then. Sorry could not be of much help on this.

Agree but the stick poll rate being vastly higher than your FPS along with your 60hz monitor with vsync enabled has to interpolate the digital inputs between each of the frames you monitor outputs. It's got nothing to do with the renderer itself but more to do with the time your peripherals have to fit inputs from your joystick in between each frame shown, this can also be exaggerated if you have multiple devices connected to a hub or if you use any form of USB extension lead. might be worth disabling vsync just to test. Here is an example:

Do you have vsync enabled? This causes input lag.

I think that the beta needs to be take off the main website page and put into the forums as a link so that people are not just clicking it to get all the latest shinny stuff without first seeing and understanding what it is they are letting themselves in for.

Try this https://skyvector.com/

Dose this bug even have any sort of priority attached to it as it now happens in stable as well as beta versions. I also just noticed that the sun glare off cockpit displays also renders incorrect in each eye..

The Radar elevation is broken for TWS, I’m sure there are other issues linked to this that are causing random contacts fading and popping in. RWS seems to have a better chance at locking up a target, but only marginally.

Stabilator movement seems a little slower in movement when looking outside the jet when going from neutral to full deflection, maybe this has something to do with it? There are videos on the internet that can be found to compare when doing a quick search.

Completely agree ED are doing a great job however there is no one out there that comes close to modern air combat simulation other than ED which is bad unfortunately..

Unfortunately as it currently stands there is no competition for ED and as such they have the luxury of saying "play our game our way or don’t play modern combat flight sims". Once a competitive company comes along (looking at you micropros) then we could see a shift in mentality. Healthy competition is needed.

That switch that’s being talked about on the O2 panel has an option to force air under pressure into the mask as well as inflating the rear bladder in the back of the pilots helmet to aid in AGSM breathing, by default this is off. To enable move the switch from the on position all the way up unfortunately I don’t think this currently modelled.

I have noticed this and there are serval posts kicking around the forums that also report this issue, I’m using the rift CV1 and I have this issue mainly with clouds and some shadows. I have tried several methods people have suggested to help fix this problem an none have really helped at all. I think there is a deeper issue as the latest patch was quite extensive and this problem still has no fix. I’m sure it’s being worked on but I think it’s probably far more complicated than it first seems otherwise it would have probably been addressed by now.

Thanks for that....

Install the stable release and forget the beta, most of your issues will disappear.

I hope not because that means then it would have been a year since a stable update, last we had was back in December..

Just as a thought I noticed you mentioned the thrustmaster Calibration tool if possible can you delete this program? My school of thought here is that you have 3 programs all using calibration methods Windows/TUSBA/thrustmaster. Windows you can’t do anything about as it detects as an HID component but you have set the calibration through the TUSBA software set, im wondering if the thrustmaster software is screwing with the already calibrated throttle., This is where DCS might be tripping over itself.

Have you tried running the windows calibration tool? Maybe this might bring it back in line.