Sirbum

why not try out DCS Liberation. just google it and you will find the github page. It generates a dynamic mission campaign and is fairly easy to install.

So it seems that no matter what module I fly...Other then the AV8B....my controller settings will not work unless i map them to the _Game version. Another words, the F18 will only recognize my controller mappings if i put them on the F18_Game and not the F18_Sim. same for the A10C_2, as well as the F16. but i want to be able to map all the settings that are in the _Sim version but when i do, the game just doesn't recognize them. I thought it may have been an issue with the Logitech software but, if that was the case then it wouldn't only work in the game version of the profiles. Seems like DCS is only loading the _Game profile and not the _Sim one? the AV8B module i don't seem to have any issues with tho. its the only plane i can actually fly right now because of this. I have also tried to download profiles for the X56 in the user downloads and try those out, and still nothing. I have even gone through and deleted all categories for both _Game and _sim with no luck. I am at a loss here and really want to be able to fly all the modules as I use to be able too. EDIT: So i figured out my issue. reading another thread it appears that if you have a setting checked called simple avionics i think it is, then this will mess up all your mappings for _sim. reading the note near it, it didnt say anything about making it use the _Game mappings but it appears to do that. soon as i unchecked that i was up and flying the A10C2

Too be honest i almost think i get better performance with the G2 now then i did with my Rift S. with my Rift S i was struggling to keep 25-30 FPS normally. and at the time i didnt know anything about Frames per millisecond. i do know that my Rift S was always in the negative for Headroom. now i switch to the G2 with the exact same rig, and as i mentioned above i am getting 45 constant, and smooth with better graphics. I think this is due to the clarity? over the Rift S and there being no screen door effect. Also i think the G2 is brighter then the Rift S.

i made the jump about 1 month ago because my Rift S just died after two years, and i can tell you OMG the difference is night and day. First off the colors are omg insane. I mean i can bright colors now. And i can read everything in the cockpit. Even in the new A 10 C II that i couldn't before. performance wise its a little more beefer but i was able to get mine dialed in so that i get 14-16 Frames per millisecond which allows me to stay capped at 45 FPS with motion reprojection for smoothness with no issues. all of this is with I7-10700 Nvidea RTX 2070 Nvme drive 32 Gigs of ram Oh and the biggest difference from the Rift S, is that there is no longer any Screen door effect at all. only downside i have ran into is, the sweet spot is fairly small. i find myself having to look down more often to see very clear. where as with the Rift S you could just move your eyes. But i hear if you mod the Face insert this opens the sweet spot a lot. I just haven't done it yet. My personal opinion on it is make the change.

so before this i was running DCS at .5 PD inside DCS and 230% resolution in SteamVR and was getting about 16.2-17.8 Frames per mili Second on the ground at an airport. with this put in, and leaving it at the .77 and everything else default i went down to 14.2-15 FPMS, which really is a big differance. Being that anything about 19 starting becoming jittery. So because of this i was able to up my SteamVR resolution to 400% which is like 4K being DCS was down to .5 and on the ground i am getting 16-17 FPMS and up in the air it drops to 14-15FPMS. So this really helped alot. all this is on the Reverb G2 with my system being I-7 10700 RTX 2070 no overclock 32 Gigs of 3200 corsair vengence ram Nvme disk EDIT: so just to add a little more to this, i just now finished playing a two hour stint in the harrier, do the training missions and man was it fun. like I said on the ground i was averaging about 17MS in the one i was doing, but it was smooth with the FPS locked at 45 with motion smoothing. and being that I just went from the Rift S to the Reverb G2 on this same system, man was that just nice looking. The mission I was in actually had a helio come flying in and land and for the first time I was actually able to see the Red and Green lights blinking lol. Sounds mondain but you just don't get the colors like that in the Rift S. Only thing i wish i could get rid of now is the damn Shimmering. I get a fair amount of that, but no matter what i have tried nothing really seems to make that go away. maybe if i went higher with the SS% but I don't want to get to a point where i start getting ghosting while on the ground. So I think I can live with it.

i actully called in yesterday and ordered a new cable with out my Headset showing a warrenty because of some glitch i guess. Just bought my headset three days ago and i guess when they first came out something happened and not all headset warrentys got entered. anyways he ordered the new cable for me with no issues after a little back and forth about my MB. and i recieved it today at 10AM. So the turn around was like 15 hours?

so i have figured out that this all has to do with the F18, because i just installed the Av8B and everything works just fine. So not sure what the issue is with the F18. so i think i am going to put this into the bugs area.

so here is a test i just tried after you said something about it trying to use another profile. i went back into the game with only my throttle connected. i went into the game and i cleared all of the column for the throttle as well as the axis under the F18_Sim, this is the one i always use and have always used. but i then switched over to F18_Game and all i set was the Thrust under axis, went back into the game and bam. it moved my throttle only. nothing else. so i went back into controls and up at the top left it showed F18_SIM but nothing was mapped. so i switched over to the game one took out the mapping and bam i had nothing. So i am at a complete loss here because if i map the axis under Game it works but not Sim. and if you use only Game you lose a lot of Mappings. EDIT: so i can definantly say now the issue is that even though i set the mappings for F18_SIM it is using the _Game, because i just went back in to the game with out VR at all, and only way i could get the throttle to work was if i mapped it under F18_Game. under Sim it would do the same thing it was doing in VR. lol and all of this is with a fresh install of DCS. thats why im only doing it in the F18 because i havnt downloaded all the others yet

i am flying the F18 right now. But here is something i am wondering. say i set up my throttle, then i setup my stick. now i click on the throttle column and i hit save profile. it saves. now i click on the stick profile and instead of saving a file for the column it asks me to overwrite. its only saving one file, not two.

when i save a profile it doesnt matter what column i have clicked it saves it to the same file. Should it not be doing this? i thought it use to be that it saved one for throttle and one for stick but mine does not seem to with my X56. wondering if this is the reason my Throttle is trying to move my stick

Yep i took a look and nothing. which is what boggles my mind. i even kicked out the profile mapping as HTML to see that it showed the correct axis mappings in there, and it does. The Vive controller that is in there isnt mapped to anything. But then i even turned off the G2 controller while in game and still same damn thing. only axis that seems to work is the stick left,right, up and down. Funny thing is that with the throttle, like i said when i move it up down it moves the stick up and down at an angle. and when i turn one of the knobs that i have on there it moves the feet pedals, so more or less it works the rudder lol. but that knob is not even mapped at all. sucks so bad because i waited so long to get back in with VR and seems i can only play while not in VR again

yep checked that as well lol. for what ever reason it sees them as Vive controllers for the G2 but none the less there were no mappings. and like i said i actually turned my controller off to see if that was the problem but it changed nothing. I dont think the issue is the hand controller for the G2 i think it has to do with the headset just dont know what the heck to check other then what i have. i am going to see if i still have my old X52 and see if it happens with that as well.

oh i see. well either way the Headset is working just fine. and the controllers are plugged into the wall power as I had said so i dont think that is the issue. I may flop it around though and see if it changes anything

nope this isnt it for a couple reason. 1. the x56 is plugged into a powered USB hub not on the mother board 2. the G2 is plugged into the Video card and the G2 actually has a power cord that powers the headset. They changed that due to being power hungry. no something else seems to be conflicting in DCS I just don't know what. i tried changing the G2 controller settings in steam to see if that was it but that did nothing either. I even turned the controller off while in game to see if it would change.

when you check in steam settings, what do mean. I still want to be able to use the controller while i am in the game, for like switches and stuff. but do you mean in here?

So I just returned to DCS after about 6 months due to my Rift S taking a crap and not wanting to fly with out VR. Yesterday I received my new HP G2 and i spent most of the day in DCS resetting up all the settings to get a good picture versus FPS per Millisecond. Anyway, i got it dialed in fairly good and must say the clarity over the Rift S is ungodly. But the issue I am having is when I went to setup my controllers, I mapped my throttle in the Axis window to Thrust and Radar i think it was. Then i mapped my Stick to the Pitch, Roll, ETC. and I saved that profile out as mine. Started back into the game and went to take off but noticed that when i move my Throttle, it doesn't move the throttle in game, it moves the Stick instead. I was like HUH. so i went back in to controls and double checked and they were still there correctly. when I would move my throttle it would show the throttle moving. I went through this on every module for about 3 hours. Finally i said the hell with it and I completely uninstalled DCS and reinstalled it. First thing I did, was went into the game with no VR ticked nothing, just normal 2D gameplay and i set up just the axis for the plane. Throttle, pitch etc. went to take off and everything worked perfect. Throttle moved what it should and stick moved what it should. So i was like ok well guess reinstalling must have fixed some file. So i went back over and put a Tick mark onto Enable VR so that i could close out, come back in and set everything up again. Soon as i got back in, i checked that my controllers were still mapped correctly and they were, so i went to take off and BAM right back to the same thing. So i have figured out, that something with the HP G2 is causing DCS to not work with my controllers correctly. I don't know what to do to fix this. Has anyone else had this issue with a G2 and controllers? or any VR headset and controllers, and if so could you please tell me what to do to fix it. i really want to get back to flying in VR lol.

check to see what you have the clouds at. i think it defaults to standard, but the new clouds are hard on a system. so you could turn them down some and then maybe get back some of your PD. also there is a new slider for trees i believe it is. try turning that down. it may be rendering more trees now then before, and that may be why you are seeing less performace.

mirror eye source is just for what shows on the desktop. it doesnt do anything for you in VR. its for people who stream the game. but if you are using the Rift s then you can just set that to both eyes. The pointer is being looked at now. for now if you uncheck palm button in the vr settings the controller thumbsticks will once again work as they did before.

this has already been reported in other posts. there is a fix coming hopefully

yes by deslecting the hand palm box, the pointer now works as far as turning knobs or flipping stwitches. doesnt bring the laser back, but at least i can somewhat use the hand controllers again, with the Rift S at least

LoL completely agree about the VR free thing. as well as most players out there don't have 2K cockpit setups that they play with. that allows them all kinds of room to the sides to reach down and hit buttons. I am fairly sure there are a lot more players playing at a desk then there are in a home built cockpit, whether in VR or not.

you are totally correct and I agree with you. If they can change it so that we as the consumer can toggle what we want on and off that would be a Win/Win. that way players as yourself who have a cockpit and the room can use it the way it is now, and players as myself who are not able to can go back to the old way. I am not asking for it to be changed back with no option to keep the new way.

i just turned off the hand all togeather for now, until they bring it back lol. back to using the mouse which sucks but at least i can get to crap.

yeh reaching things with the glove for me is a no go because i play at a desk lol, so soon as i try to go for buttons down and to the right or left, bam i run right into my desk. Not sure why they decided to make this change, and it would be fine as long as we had the option to revert if we liked.

The new Glove that is in VR now is way to big because i have my PD in game set a little higher then normal. Also, the lazer that use to show from the tip of the finger to what ever control i am trying to work, no longer shows. Most of the time the + now points outside of the plane even though the tool tip for what ever button im on shows. This is making working the knobs way harder then it use to be. Is there a way to switch back to the old version of the glove in game? this is all on the Oculus Rift S by the way. dcs.log