Xupicor

They still didn't map the throttle axis to in-cockpit throttle 1:1, though.

Is anyone here fluent in 'Lua Console' / 'Hub Scripts'? I wanted to write a proof of concept "coordinates to cockpit inputs" where I would read in coordinates and translate them to button inputs needed to automatically punch them in, something "DCS: The Way" is doing already. However, the code - as unoptimized and primitive as it is - seems to work fine in all respects but the crucial one. Only the first and last input seems to get sent and actually recognized by DCS. Is there a caveat to using `hub.sendSimCommand()`? I'm sending the button names taken from the docs (Control Reference), yet only the AMPCD ones get acted upon properly. UFC_OC1 doesn't get activated for some reason - but if I play with the delay and punch the button in-cockpit myself, the numbers show up in the end (so UFC_0 through UFC_9 work? Kinda?), though, not the last one, for some reason, and UFC_ENT doesn't seem to do anything either. if not hub then -- for testing in cli hub = { sendSimCommand = function(c, v) end } end function sleep(n) -- seconds local t0 = os.clock() while os.clock() - t0 <= n do -- just a busy loop - I couldn't find a way to do it smarter in hub environment end end function press(command) hub.sendSimCommand(command, "1") sleep(1) -- I want to see it done slowly hub.sendSimCommand(command, "0") sleep(1) -- I want to see it done slowly end local command_to_buttons = { ["N"] = "UFC_2", ["S"] = "UFC_8", ["E"] = "UFC_6", ["W"] = "UFC_4", ["0"] = "UFC_0", ["1"] = "UFC_1", ["2"] = "UFC_2", ["3"] = "UFC_3", ["4"] = "UFC_4", ["5"] = "UFC_5", ["6"] = "UFC_6", ["7"] = "UFC_7", ["8"] = "UFC_8", ["9"] = "UFC_9", [","] = "UFC_ENT", ["'"] = "UFC_ENT", ["."] = "UFC_ENT", ["U"] = "AMPCD_PB_05", [">"] = "AMPCD_PB_12", [":"] = "UFC_OS1", ["f"] = "UFC_OS3", ["t"] = "UFC_OS1", } function punch_in_single_coord(sanitized_coord) for c in string.gmatch(sanitized_coord, ".") do press(command_to_buttons[c]) --print(command_to_buttons[c]) end end function punch_it_in() local matches = { "U:N4134.>", --"U:N4134.0411'E4136.9865'ft155.>", -- "U:N4134.0411'E4136.9865'ft155.>", -- "U:N4330.8198'E4338.3728'ft1411.>", -- "U:N4244.4262'E4404.3242'ft11001.>", -- "U:N4314.8299'E4426.1757'ft1370.>", } for _,m in pairs(matches) do punch_in_single_coord(m) end end punch_it_in() The docs don't even include any wait/sleep function between an example of those calls, so I'm unsure if I would need them in the end or not. I'd think so, since otherwise it would be a barrage of inputs... They also say: But I have no idea what it's supposed to mean. Buffer size of 10... what? 10 commands? Or do they phrase a time delay between the calls as "buffer" and it's miliseconds or something? No clue. That's basically all there is about it in the docs -- that I found... I'd appreciate any input. I'm new to Lua, so maybe there's something obvious in there. (Not as new to programming to see that there are probably faster ways to loop just using normal indexing, but that's not the showstopper here. I just wanted to use the fancy Lua stuff. ) The way you'd test this is just copy paste this to 'Lua Console' in DCS BIOS Dashboard and execute. This is for the Hornet and you have to be in HSI 'DATA' screen with PRECISE boxed in, that's on your AMPCD.

One more then. Since the Scratchpad mod already is doing such a great job at selecting stuff on the map and dumping coords to file - in flat and VR both - and that's just by using lua script - could you either mimic it or possibly work with it? I'd love it if I could point at a scratchpad file in TheWay where my coordinates are and TheWay would then parse them, take the ones it needs for a given module and punch them in. Using Lua I can do the parsing part and I'm trying to do the punching in with DCS-BIOS, but there are some issues roadblocking me at the moment. My solution would still need an external app - DCS BIOS - which I have no problem using, but it's there just for one function, basically. You could do it better and already have a working infrastructure. If you could make an option for using a file that would work with coordinates spat out by the Scratchpad mod, that would be quite awesome. Even better if you could incorporate or learn from Scratchpad's method of getting the coordinates since it works for VR too.

I don't see the dot in VR, so doing it while peeking from under the headset is just about as annoying as just punching the stuff by hand in anyway. Multiple software hooks for a keyboard/gamepad button presses while DCS is in focus and doesn't trigger antiviruses - AHK, VoiceAttack, LuaMacros, SRS, etc. So definitely possible. You could also use parameters - then we could bind stuff in VA, etc, and we'd call, as an example: "theway.exe -start", "theway.exe -add_point", "theway.exe -clear" or "theway.exe -punch_it_in". The instance run with a parameter would communicate with the main instance and tell it what to do. Just an idea. Very cool program, wish I could use it.

I just use Notepad++ for the log file with custom language defined for pretty colors and such, but this looks very nice. Not sure the link works, though.

This would be a glorious development. I'd love to sit back on my other PC and have the mission editor to tinker in outside of the game.

Seems like you're trying to be awfully slippery there, Rainmaker... Anyway, regardless of the real F-15 throttle behavior - it would be a nice quality of life option for those who need it.

I just flew in MP with Yak-52, Easy Comms off, of course, as all the other "easy" settings - they're disabled on my side, but more importantly - on the server mission. Pressing '\' didn't bring the comms menu up, but pressing '3' worked just fine, that's "Radio Button (call radio menu)" binding.

Thankfully we got a lot more space now, but still have to resize stuff to fit my devices on one screen.

Holy moly...

Yeah, I've got the exact same issue. I just installed it clean and it wouldn't work out of the box. I can delete `KneeboardBuilder.exe.Config` and it will ask for initial settings but when that's filled it restarts and always bugs out with that error. And here I just wanted to use it to convert some pdfs for A29B kneeboards. Oh well... EDIT: Okay, so I deleted the config file, chose "Stable" in the DCS World Install Directory (not custom, no dir actually picked) and saved the settings. After restart KB just says that DCS isn't installed in whatever directory, that's alright with me because... It doesn't crash! So I can actually use it now - import and convert pdfs works just fine, just can't use the more advanced stuff I guess.

Honestly can't wait for this. I wouldn't mind if this project eventually went professional too, I'd pay some bucks for it at that point!

I installed Ultraleap Tracking software and while hand tracking worked out of the box in DCS, no dll shenanigans necessary (am I missing something?) but it broke OpenXR. After uninstalling it - OpenXR started working again. Did any of you get that as well? As for the tracking, it was... not perfect, let's say, and way worse in usability than PointCTRL. It was the Stereo kit with wider FOV.

I went with a clean install about 10 months ago or so and I couldn't run VR anymore. WMR wouldn't install properly. I went through the MS forums and found a buried topic about Win11 having some problem with it -- the recommended solution that also worked for me was installing Win10 and then upgrading to 11. WMR magically worked fine after that. I had other issues though, some DCS VR performance related (stutters) and went back to 10 where it worked better. I'm still holding off the upgrade since then. TLDR: if you run DCS in VR with WMR headset like G2 - beware. Maybe they fixed it by now, though. Hopefully. If not, Win10 and in-place upgrade to 11 may be the better way. Or just holding on 10 for now.

How do you know you aligned it correctly? Did you check it with PNVS imagery on? If I'm not mistaken it still might be the case that you have to boresight as if it's rendered in stereo even if you have it in mono. But, regardless if I'm right or not - again - check it with PNVS every time.

What doesn't work? You can still boresight reasonably well in VR - it's just a bit trickier to do because, like you said, you can't pause it, and if you focus on the rings you'll see two crosses - but that's just how it is with stereoscopic vision in reality too. Check your boresight with how the PNVS image aligns. It might take a few tries, but if well boresighted and with autoranging on the gun is quite precise.

I've seen this posted a few times, but I own a Warthog and do not notice any baked in deadzone (much less of a "few degrees") with it, and I do have an extension of 20cm. Maybe this was fixed in a newer firmware? Any source for that claim to begin with?

Every time I boot into DCS I have to resize all the columns in Adjust Controls settings page if I want to, well, adjust anything. This is remembered while the game is running, but lost as soon as you close it. Can we please get the game to remember these set sizes between restarts? It would be just a small quality of life thing, but much appreciated.

I just tried it with the latest OB - didn't seem to be doing anything, I didn't see any droplets. It's quite a bummer. I hope 2.8 brings a fix with the weather stuff, but not going to hold my breath. Such a pity canopy effects are so underdeveloped and pushed far to the side - especially in VR...

Is there a way to stop the skybox in loadout editor from rotating and manually set its position? Through Lua somewhere, possibly?

You can get that through modifying the lua files too. I recommend these two mods: https://github.com/Quaggles/dcs-input-command-injector -- to inject custom input commands stored in your Saved Games folder (so that if an update breaks them, you just fix one place where the mod is injected, not 15 different files in the game installation directory) https://github.com/Munkwolf/dcs-community-keybinds -- this is a collection of custom commands, many of which are there to use warthog-type On-Off-On switches with DCS ingame cockpit switches that do just that - they make it easy for you to use the middle positions on many switches. In Mig21 input file (Saved Games\DCS\InputCommands\MiG-21bis\Input\MiG-21\joystick\default.lua) I modified the lines responsible for custom gear commands: -- Gears {cockpit_device_id = devices.GEARS, pressed = device_commands.GearHandleFixator, down = device_commands.GearLever, up = device_commands.GearLever, value_down = -1, value_up = 0, value_pressed = 0, name = _('Gears Handle - DOWN else NEUTRAL (3-way Switch Down) + Lock'), category = {_('Gears, brakes and chute'), _('Custom')}}, {cockpit_device_id = devices.GEARS, pressed = device_commands.GearHandleFixator, down = device_commands.GearLever, up = device_commands.GearLever, value_down = 1, value_up = 0, value_pressed = 1, name = _('Gears Handle - UP else NEUTRAL (3-way Switch Up) + Unlock'), category = {_('Gears, brakes and chute'), _('Custom')}}, What this gives me is: When the gear lever is in neutral position switch up unlocks the "Gear Handle Lock". It doesn't move the gear handle up - even though that's what I wanted originally, I prefer it that way, because it makes me actuate the locking mechanism. Then I move the physical switch to neutral position and move it up again - that actuates the actual gear handle up. When I actuate the switch down from neutral position I get the gear handle to go down and the locking mechanism to lock. I just tested it - works fine.

I mean the button you can click that's usually under your scroll-wheel. Press on the mouse wheel and MOUSE3 should click - that's the one I mean.

In a lot of modules it's the mouse wheel button - if it doesn't work immediately (enters transpose mode instead) then double click it. Also - hold, movie view and release should be possible with lua editing. I may take a look at that.

I've noticed this too -- it's quite obvious even to a newbie pilot like me that if you try to center the ball in the Huey at speed something is completely off. For that reason, sadly, I ignore it completely and fly by what I see out the window and that gives me better results. I'd also say the ball doesn't quite work right in the Apache, since if I try to follow it religiously I risk departing... Again, I tend to fly by what I see outside with regards to sideslip and ball centering, makes it much safer for me. That might be just bad newbie piloting on my part in the Apache, though. It's saddening to see this issue still being seemingly ignored. I know ED uses SMEs when developing modules, but SMEs can make mistakes too, especially with so many different models of Hueys out there. That one post with different models pictured with tail rotors on different sides of the tail makes me think at least some SMEs flew different models than the one that's depicted by the sim and some facts just went under the radar. I'm not even judging - things happen, it's not the end of the world. It would just be nice to have that fixed. Especially that the FM looks correct, and it's "just" the indicator that does something funky.

I just ran an instant action mission in Mig-21 and it seems I can bind mouse buttons to "Zoom in slow" and "Zoom out slow" just fine now. Can you confirm it works for you as well? Seems they fixed it? As for your changes: any reason why you used "pressed" instead of "down"? I used "down" and it worked. for the changes I described you should use the files in the main game installation directory, not the Saved Games/DCS directory. However, that makes me think if we can't do it in a better way yet... Standby on that. you need unique names for keybinds - add " ALT" or something in the end to make them different than the ones already in there. Anyway, I tried it and it didn't work for me in mouse/default.lua - however I could add the lines to keyboard/default.lua and it did show up (I just used alternate names) No need to do that, though, since they are already there and you can just change the existing lines.