Gogsie59

Thank you, in any case I'm really enjoying the campaign.

Thanks, yes this was it, my fault totally. Too used to putting in just the last 8 digits. Thanks again.

After being informed to go to the oil platform I input the coordinates which are listed as waypoint 6 but this point me towards land and not an oil rig. I check the coordinates which are correct so I am lost at what to do. I believe I could just follow saber 3-1 who goes off in the opposite direction but if thats the case whats the point of inputting the waypoint. Both times ive tried it and both times the waypoint is miles away on land.

I tried this today, no joy on my end, in fact it caused dcs to crash every time. In the panel it tells me no module found and all the indicators are red. Im using a G2 and not with steam vr. Nice idea but a manual would be nice with instructions instead of the bare bones that are given. One bit says to set bindings and there is a highlighted bit of text but guess what its a blank page. Im out.

NEW: Added support for AMD FSR 2, FidelityFX Super Resolution (FSR) also using an upscaling algorithm to improve performance. Also like DLSS, it will have little to no effect if you are CPU-limited. WIP.

Do you not have to be using the beta version, your link is for the standard version. I could be wrong though.

Now when I try to do this mission I sit in total silence, no hints at what to do. Is there any way to reset this campaign back to scratch as something is really borked here?

It's maybe just me but when I try the first mission and he tells me to follow I can't move because the wheel chocks are in place and nothing I do removes them. I don't remember being told to remove them and using the menu to ground doesn't do anything so I'm well and truly stuck. Any tips out there?

As previously stated in another post I cant get past the first mission. A kind gentleman pointed to a video of the campaign and I am following it to a T but it keeps failing me saying I failed to destroy whoever it is at way point 3. I fired my jsow when told to and the target is in range. I then fly past the tower and see it collapse and Im thrown back to the carrier to start again. HELP. What am I doing wrong.

Thanks, I'll give it another go tomorrow, the video helped.

I must be really hopeless at this, I cant even get past mission one, It keeps failing me for failing to destroy jsow target at way point 3. I do fire at it but no joy, round and round I go, rinse repeat. Gets a bit boring and I end up shutting it down. Here was me thinking this campaign is supposed to be easyish for beginners. What am I doing wrong.

Thanks, yes I saw that and was trying to copy but it says invalid. In anycase mine doesnt look like that it doesnt say testing 2nd, do i need to add that. thank you thank you, exactly what I was looking for. You are a gentleman.

Where do i add the --force_enable_VR --force_OpenXR I tried after where it says dcs.exe it said that was invalid, I tried before it, again invalid. Can someone please put up a pic of what I'm meant to do. I know for all you clever clogs who do this sort of thing its a no brainer but if you don't know , you don't know. Much appreciated.

Thanks, excellent.

Sorry for being dense, so for example I have a G2 what do I have to do to make it run native open xr??

Same problem I have,G2 AND 6950XT. I'll give that driver a go. Good find.

Exactly what I'm getting. G2, AMD 6950XT.

G2, AMD 6950xt, blinking in right eye, and eventually green screen of death during game play. First time this has happened and all after updating to latest beta. I used open composite before, did not use open xr toolkit as the performance without was excellent.

Can someone confirm that I can leave Open composite on my system and when I start dcs, stand alone, with my G2 it will not interfere with the the native open xr which is now included. I use open composite for other games and don't want to get rid of it. I certainly don't want to use steam vr.

Thanks, yes it's working flawlessly at the moment. Slew is brilliant now and chuffed with it.

I have had the slew upgrade installed for about 6 weeks, all went fine and worked perfectly. I installed the new firmware for the thumbstick last week which also worked fine or so I thought until I found that the hat switch on the right hand side of the throttle was going crazy as were all the switches on the right hand side of The throttle. When I checked with the Windows game controller it showed that when I used the hat switch all the other hat switch buttons were lighting up. The other switches, China hat etc would also light up other button positions. Reinstalled the firmware, reset the calibration in the window cal app and then recalibrate with the drumstick recap app. Still no joy. As a last resort I used the Windows calibration tool and bingo all buttons and hat switches are working again. I know it says never to use the Windows calibration tool so I'm wondering if I've mucked something up and if I need to do anything to get it working with the thrustmaster calibration.

I have got my throttle buttons working perfectly again, I opened the Windows calibration via joy.cpl in the run window. As I checked all the switches on the right throttle numerous buttons were being activated when I pressed for example button 7, same for all the other buttons the numbers were flashing on and off as if I was pressing them. I recalibrated the throttle with the Windows calibration tool and bingo all working as it should. Very strange that this happened but just a heads up to anyone who comes across this problem.

I have got my throttle buttons working perfectly again, I opened the Windows calibration via joy.cpl in the run window. As I checked all the switches on the right throttle numerous buttons were being activated when I pressed for example button 7, same for all the other buttons the numbers were flashing on and off as if I was pressing them. I recalibrated the throttle with the Windows calibration tool and bingo all working as it should. Very strange that this happened but just a heads up to anyone who comes across this problem. Thanks again to Willie for getting back to me. Grant.

Thanks Willie, Grant.

Hey Wali, did you ever find out what caused the switch glitch, I have the same problem and would appreciate any tips to solve it. Thanks.