dfoxpro

Hi I want to set just once all the axis curves and general-trivial buttons for all my planes. I supposed editing those in the controls general category would be enough for all the planes, but no, no plane recognizes any of the default(folder)~general(category) keybind/axis-curves I'd set; even cleaning the binding for the specific plane. So ¿How can I use the general category to set all my planes binds? or ¿Is mandatory to set plane by plane with the same binds? here is an example excerpt of the default file ### .../Saved Games/DCS.openbeta/Config/Input/Default/joystick ... ["a2003cdnil"] = { ["added"] = { [1] = { ["filter"] = { ["curvature"] = { [1] = -0.33, }, ["deadzone"] = 0, ["hardwareDetent"] = false, ["hardwareDetentAB"] = 0, ["hardwareDetentMax"] = 0, ["invert"] = false, ["saturationX"] = 1, ["saturationY"] = 0.5, ["slider"] = true, }, ["key"] = "JOY_SLIDER2", }, [2] = { ["filter"] = { ["curvature"] = { [1] = -0.3, }, ["deadzone"] = 0, ["hardwareDetent"] = false, ["hardwareDetentAB"] = 0, ["hardwareDetentMax"] = 0, ["invert"] = true, ["saturationX"] = 1, ["saturationY"] = 0.5, ["slider"] = true, }, ["key"] = "JOY_Y", }, }, ["name"] = "Rudder", ["removed"] = { [1] = { ["key"] = "JOY_RZ", }, }, }, ["a2004cdnil"] = { ["name"] = "Thrust", ["removed"] = { [1] = { ["key"] = "JOY_Z", }, }, }, ... and this is an example excerpt of jf17 file ["a2003cdnil"] = { ["name"] = "Rudder", ["removed"] = { [1] = { ["key"] = "JOY_RZ", }, }, }, G27 Racing Wheel {A76C3DB0-396D-11ec-8001-444553540000}.diff.lua

Hi! I have a couple of stand alone modules related to FC3, I update today(feb25) and tested the planes and see no changes, so; ¿Are the stand alone modules with the new textures? Notes: · I'm using vr+fsr I know it now look kinda blurry with the fsr but I know the difference. · I double check using the default texture (I have the blue english texturepack) · I also have texture config to high · Also can you fix the carrier weird reflections pls ?(the red lines in surface by the mirror) · Is the su25t with new textures? (I tried that too without luck) Edit 2: Looks like the new texture are running (based on switch red colour in the video) but it looks to blurry vs the video, vs a full module (I have the JF17) but

- Have you updated your G2 Firmware: Yes I did - Have you turned off hot swapping inside DCS? How can I do that? - and or try a connection to a powered usb hub. On that...: I found that using the usb c2a adaptor and using another usb port in the board fix the disconnection issue with my HMD, any way I can still reproduce the issue connecting to the (only) usb C in the board (asus crosshair 8 impact). note again this issue only happens in DCS, other heavy games does normally even with the usb problem.

Hi All Currently I have an stuttering problem with my reverb g2 and (only) DCS, I "debug™" my problem and what I found is every time a USB device is connected to the PC the game stutters. In my very own case, I believe, the VR-cable have a broken cable for the HMD audio, triggering disconnection and re-connection of the audio device -> leading to an unplayable game. How to reproduce: Even without VR you can use any related USB device, like a controller or audio-device start a game and then physically disconnect the device, this will trigger the freezing. [see example vídeos] Example video in VR here: Expected behaviour: DCS not freezing every time a USB device is (dis/re-)connected?? I attach the log with the device (un)plug info correlated to the stutters 2021-12-05 09:17:11.445 INFO APP: Device unplugged: \\?\USB#VID_03F0&PID_1841#8&7392e18&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 2021-12-05 09:17:24.554 INFO APP: Device plugged: \\?\USB#VID_03F0&PID_1841#8&7392e18&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed} PLEASE ED-team, take a look on this issue it eventually will affect any random wired-vr user or wired-usb-(controller/audio) user dcs.log

I did my own testing with my G2 and found: 1 My cable has possibly broken signals for the audio 2 This is leading to audio device disconnect>re-connect 3 Every time this happens there is a stutter in the game. Please take note on the next vídeo every time the USB logo appears in the notification area there is a spike in CPU timing (then the GPU) and the stutters happens Possible "Quickfix™": use the new G2 cable?? Various notes: · I also did a report on how to reproduce this stutter without VR, just disconnecting > re-connecting a USB device like an USB-audio here. · This is not happen with all the other VR games that I own. · I start to suspect this when the HMD mic and audio suddenly stops both for DCS game audio and SRS mic&audio. · I know a solution is to ask warranty on the cable (It's on my way) but it's also kinda anoying DCS is the only game suffering this issue. · Expected solution: DCS not freezing every time a usb device is (dis/re-)connected?? PLEASE ED-team, take a look on this issue

The flanker for example show the WP number in the radar display, the number in the hud of the su25 is because it lacks the extra screen to show a detailed info on that (I suppose)

Hi Bignewy, Is there any update on this issue? Also related, the su25(T) is missing the trim reset action; it'll be nice if ED fix those control/inputs inconsistencies

After topic: I bought the amurican carrier DLC thanks to your comment, I have hope ED will feature pair the US and Russian carriers.

I'm also having the same problem, I set graphics to the bare minimum and dcs process to high priority without any luck, and this is new like one or two patches ago. Also I'm running an amd card.

Hi! I want to know if there is a roadmap or ToDo list to lookup the future features of the Kuznetsov carrier in the super carrier DLC... Personally I want to see personal in this carrier and the elevators working.

After more digging I found that the option "set controllers to hotas position" (or something like this) is the trigger to this very bug, disabling this option restore the expected behaviour. Anyway, it's still wrong for some specific ships to be broken with this option, especially when some other ships from the same package and the same quality/type ("ssm"[standard system model?] I believe) work just fine. It's like the other bug-reports, where the su25(T) planes has missing common controls vs the other FC3/SSM planes, like the axis wheel brake and reset trim for example; It should be a more consistent control experience across planes.

No, only keyboard and steam input (xbox360 controller for DCS) for the joysticks, btw I'm using the stand alone game not the steam game. Any way, yesterday I did more test with(out) vr and got the same results on su 33 (both fails vr and flat-screen) su27(only fails in vr), migs (both fails in vr and flat-screen) and su25 non T(both fails in vr and flat-screen with special note); I double check the key-bind was valid [See attach images]. and a special note on su25: when I press any start engine key-bind, the indicators lights blinks for a jiffy without engine start [See vídeo]. finally note this is not happen on all airships, for example, the su25T has no problems, the su27 only fails in vr, so it sure wort the analysis and fix.

Tested (/affects) with FC3 su-33 & su-27 How to reproduce: Go to "Start up" training mission or with mission editor use a cold state plane. Now press any of the key-binds for start engines (RAlt or RCtrl or RShift + Home button). What to expect: The engine should start (sound, tachometer, throttle and light indication) What really happens: The engines keep in off state Notes: · The instructor in the tutorial recognize the start engine commands (left and right engine) and continue with the tutorial. · It is a soft-lock in many (custom-) missions and tutorials. · Tested with keyboard and also steam-input controller overlay (steam controller). Video evidence: Mission track (attachment over 5 MB) https://mega.nz/file/NwV0WJYT#BGoYmBdRsIm8OV-cAz8jt_AC_Dk0dvhO4gtK2RjfWTg Personal note, this month I'm waiting for a virpil hotas, and really really really wanna use my new toys with the Sukhoi planes

It'll be cute if there is any progress report of this issue... after 3 reported game updates, the plane still miss the bind. Anyway, nice job you all, the green light blob removal was a nice touch.

Well this is not a solution it is a workarround, a really painful workarround. also it keeps the trims in a non-center position, so every time you retake manual control it's a gamble where to point your joystick. I already try to add the reset-trim instruction to the keyboard.lua input file without any luck (the control list show the action but in gameplay does nothing). Please report this, I also research and found there are people also asking for the weel-brake axes to be a thing with the frogfoot planes.