fael097

Oculus quest hand tracking exists for years, how is this not a thing yet?

Hey, I'm having this terrible micro stuttering effect when moving my head around in VR. FPS itself is pretty good and consistent, but when I move my head around, the camera starts stuttering, like jumping all the time. If I decrease every graphics setting to the lowest possible, it improves, but doesn't go away completely. my hardware: EVGA RTX 3080 GPU AMD Ryzen 9 5900x CPU XPG M.2 NVMe SSD 1Tb (3300/3500 Mbps writing/reading speeds) ASUS ROG Crosshair VII Hero (wi-fi) x470 MoBo Oculus Rift S VR Headset Thrustmaster Warthog HOTAS Worth mentioning that this is a completely clean and fresh windows install, only basic software on it, purged all previous configs, and the stutter is worse than when I used to play DCS in VR on my old computer, which had a GTX 980 ti + ryzen 7 1800x + a slower nvme ssd. I've read a few topics about micro stuttering but I don't think any of it helps, as even lowering all settings doesn't make it go away, and my hardware should be able to handle it.

Can't find how to do it, oculus touch controllers don't appear in the input list.

brilliant, it worked. thanks!

hey, yeah it's a hid controller :thumbup:

Hey guys, does anybody know how to configure Joystick Gremlin so when I hold a button on my gamepad, the value of a virtual axis on my vJoy virtual controller increases over time, while I'm holding the button?

this is very strange. leap motion has been around for a while now, and it would solve a few hiccups with vr

does dcs support leap motion? as in can I use leap motion with a vr headset and see my hands in game and use them to flip switches?

got it!

hey, does the hornet have an energy caret indicator on the hud when landing or is it just the super hornet? The energy caret indicates acceleration / deceleration or constant speed

hey, is there a guide for sams, etc? I think I saw something once, but not quite sure where. it's hard to do certain missions without understanding how close to a sam site you can get, or even understanding what's a sam and what's not. cheers

as someone who played A LOT of f22 lightning 2 and f22 raptor when I was a kid, the SA page + awacs datalink is a life saver. it made my life so much easier and is so much more intuitive than using only the radar. however as others said, it's mostly for a/a, not much useful beyond that

I see! that makes sense now mate. I'm just not sure if I understand the need for this, specially in radar guided gun mode. I don't think they would implement this as always on in this mode if it was just additional information and not really useful, but I'm not sure how this could be actually useful, like in what situation you would rely on this

hey thanks for the research Jak, it makes a little more sense now. but is the foresight supposed to be shown at the same time as the pipper? can't you select one or the other? or as mentioned above, declutter the foresight off the screen? also, I'm still "a little" confused on the horizontal lines: so the inclination of the lines relative to my hud represents the target's roll? and if the target were to roll 90º and pull 9g he would be by the end of that line when? how is this useful? if I sense the target is going to do it and roll 90º and pull some Gs, am I supposed to aim for the end of this line? can I even do this? won't the foresight move along as I move the plane? I understand the first part with the 1g and 9g + symbols, but still no clue on the horizontal lines

I wonder what reverb's screen looks like compared to the rift or rift S

thanks for all your input. I also found this video, if anyone is interested: (nevermind the accent) it's not exactly what you'd see, but you can have an idea. sometimes it looks like just an average/good upgrade but other times it looks like a major improvement from the cv1. I'm just glad I didn't buy the Vive, it looks nasty. never used one though but it's looking good, I'm definitely gonna give it a shot

exactly

Glad I'm not the only one in confusion. Hopefully someone knows better or maybe Wags to the rescue.

Hey, the guided gun is a breeze to use, very likely to hit the target, however I'm trying to understand all the symbology, and I don't quite get the FORESIGHT thing. wiki says: so the first plus sign means 1g at current attitude, that means basically not moving. ok, but then why isn't it over the target? how about the two lines, does it mean anything or just the current roll of the target? it doesn't really make any sense to me. help? :doh:

will become possible as in it's not possible right now? is there an estimate for this function?

So I turn jhmcs by turning the knob up, then it shows the helmet display and sounds, but when I disable it using the recce button I still hear the sounds? (like the annoying sound when the helmet symbols enter/leave the hud area) is it how it works? Do I need to dial the knob down to disable the sounds?

the easiest way to redo it after each update: -download and install notepad++ -make a shortcut for it wherever you want -set the shortcut to run as administrator - this is very important as it's the only way to save the files if you install DCS into the default directory -open the default.lua file that you want to mod - in this case C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick\default.lua as mentioned above -create a new file and save it with any name .lua anywhere you want, you will script your changes here and then paste it into the default.lua and save both files. why do this specifically? because notepad++ keeps the files you opened on its memory. next time you open it those two files will be there in two tabs just like when you closed it. so if you update DCS, next time you open notepad++ you will have the default.lua file back to its default state, without your modifications, and you will have your other file on another tab, so you just have to copy and paste it into the default.lua again. it's still a manual process, but trust me, it's way easier than opening windows explorer, browsing for your txt file where you saved your mods, opening with windows notepad, copying it, then browsing for default.lua, opening it with notepad, pasting it, trying to save just to realize you are not in administrator mode, then saving it elsewhere like your desktop, then realizing you saved your file as .lua.txt because notepad defaults to that and you forgot to change, then manually erasing the .txt from the file name, copying it, browsing for the default.lua folder again cause you just closed it without realizing you would need it again, then replacing the file. and repeating that every update. and also repeating that for other .lua files that you modified. seems like it's not too much trouble and that you could avoid many mistakes here and there, but it becomes a chore quickly. compare that with opening notepad++, both files are already opened that in tabs, then copying the text from one file and pasting into the other and clicking save. done. other tips: -make a new section for your custom commands on top of the original Cheats section, by adding a new header, such as --------------------------------------------- -- Mods ------------------------------------ --------------------------------------------- -Name your commands so that you won't mistake them for official commands, like adding _MOD after their names -create your own category so you can easily find in game all your custom commands. in my case I added them to the existing categories and also one called Mods that I made. like this: category = {_('Special For Joystick'), [b]_('Mods'),[/b] _('Right Vertical Panel')}}, here's what I added to my default.lua: --------------------------------------------- -- Mods ------------------------------------ --------------------------------------------- { down = hotas_commands.THROTTLE_EXTERIOR_LIGTHS, up = hotas_commands.THROTTLE_EXTERIOR_LIGTHS, cockpit_device_id = devices.HOTAS, value_down = 0.0, value_up = 1.0, name = _('Exterior Lights Switch_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Throttle Grip'), _('HOTAS')}}, { down = extlights_commands.LdgTaxi, up = extlights_commands.LdgTaxi, cockpit_device_id = devices.EXT_LIGHTS, value_down = 1.0, value_up = 0.0, name = _('Landing Gear/Taxi Lights Switch_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Left Vertical Panel')}}, { down = gear_commands.AntiSkidSw, up = gear_commands.AntiSkidSw, cockpit_device_id = devices.GEAR_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('Anti Skid Switch_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Left Vertical Panel')}}, { down = gear_commands.LaunchBarSw, up = gear_commands.LaunchBarSw, cockpit_device_id = devices.GEAR_INTERFACE, value_down = -1.0, value_up = 1.0, name = _('Launch Bar Control Switch_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Left Vertical Panel')}}, { down = iCommandPlaneGearUp, up = iCommandPlaneGearDown, name = _('Landing Gear Control Handle_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Left Vertical Panel')}}, { down = gear_commands.HookHandle, up = gear_commands.HookHandle, cockpit_device_id = devices.GEAR_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('Arresting Hook Handle_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Right Vertical Panel')}}, { down = fuel_commands.ProbeControlSw, up = fuel_commands.ProbeControlSw, cockpit_device_id = devices.FUEL_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('Probe Control Switch_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Left Vertical Panel')}}, { down = gear_commands.EmergParkHandleOnOff, up = gear_commands.EmergParkHandleOnOff, cockpit_device_id = devices.GEAR_INTERFACE, value_down = -1.0, value_up = 1.0, name = _('Parking Brake Switch_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Left Vertical Panel')}}, { down = ctrl_commands.WingFoldSelect, up = ctrl_commands.WingFoldSelect, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = -1.0, value_up = 1.0, name = _('Wing Fold Control Handle TURN_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Right Vertical Panel')}}, { down = SMS_commands.MasterArmSw, up = SMS_commands.MasterArmSw, cockpit_device_id = devices.SMS, value_down = 0.0, value_up = 1.0, name = _('Master Arm Switch - SAFE/ARM_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Instrument Panel'), _('Master Arm Panel')}}, { down = cpt_commands.CanopySwitchOpen, up = cpt_commands.CanopySwitchOpen, cockpit_device_id = devices.CPT_MECHANICS, value_down = 1.0, value_up = -1.0, name = _('Canopy Control Switch - OPEN_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Right Wall'), _('Systems')}}, I added some functionality to the TM warthog hotas. the actual hornet hotas' pinky switch is only 2 position while the warthog is 3, so I wanted to add the landing gear taxi lights to it, but since the switch is ON-OFF-ON it would be weird, I'd have to chose between having the exterior lights or the taxi lights on. so I had to add a mod to invert the behavior of the exterior lights switch, so when button is down, value is 0 (off) and when it's up value is 1. now my pinky switch works like this: both OFF / only exterior lights ON / exterior AND taxi lights ON. you can't have the taxi lights on with the exterior lights off, but that's a trade off I was willing to make. did something like this for many commands, I posted a picture of my hotas assignments somewhere once, but I changed a lot of useless stuff since then. perhaps will do it again someday. but I guess OP can work from there. I also modded a command on the default.lua file for my keyboard because some commands have the keyboard shortcut assignment disabled when you add them on your joystick default.lua. I believe it was the speedbrake, not sure hope this helps!

I'd buy a game controller usb board and a big red button (just a switch, not usb or anything) and DIY it. it seems such a waste using a usb port for only one input. there are boards such as this one: https://www.amazon.com/Gear-Falcon-General-Purpose-Joystick-Controller/dp/B01A7A3ME8/ref=sr_1_6 but I don't know if it's any good, or how cockpit builders are doing their things these days. but hey, that's just me. if you just want one button, why not?!

loadout change?

reading a lot of good things about the rift S here. I thought the improvement was marginal since the resolution didn't change that much from CV1, but the comments here tell a different story from the people who have the rift S, specially the ones coming from the og rift: do you have any difficulty reading anything? I mean, I'm afraid to buy it and then realize it's like 50% better but some stuff are still unreadable.