Lange_666

SkateZilla's one, just one icon for everything.

It's a lot closer to reality now in VR instead of the 2D version where it's more on/off. A lot of people want their sim to be as close to reality as it can get until they are annoyed by something and then all of a sudden it's not so needed any more. This ^^^^

You can't turn it off, not for the F-16 either. You can only move it up down. In 2D you get a clear view with either the visor up or down, makes it look like you can turn it on/off. In VR it's different. Topic poster is talking about the VR implementation where, unlike in 2D, you can see the edges of the visor, the nose gap and the fixation on top of the helmet. Depending on how the different headsets visualize this, it can be distracting.

Rift-S user here. For me it's just fine, it's a small gap (unlike the screenshot in the first post). The only thing that's distracting a little bit for now is the fact when moving my head from left to right (or vice versa) the small gap becomes a bit more noticeable, but not bigger, only more pronounced, in the direction i look and less noticeable in the direction i don't look which makes it "switch" a bit.

Did you try each RAM module one by one? Still error 55?

Did it boot properly after the BIOS update? If no, did the BIOS update went OK? If not, look no further than that because upgrading to Win11 before let you boot and play (although with performance issues). If you can't get into the BIOS clear the CMOS either through a jumper or by pulling out the battery. Still error 55 after that, as provided above, check RAM seatings and or faulty modules.

Kinda drastic solution if you ask me. You will probably end up with the same problem as you have now, spend quite a bit of money for no solution. I to have quite some stutters lately when in MP, mostly in VR where before it was as good as stutter free.

In the comments on the DCS User files of Thrustmaster Combined Full DX Mapping there is a post with the same error but with no solution. Digging a bit deeper into the internet cave i came across what you already tried (in white). But there's a bit more below where I found that "solution": ----------------------------------------------------- You should explain people what it does. It prevent the pc to turn on/off the device for power saving. It can be a reason for this error message. But most of the time it's because we install driver and Target in the incorrect order. Driver must be installed first, then we MUST disconnect all Target compatible peripheral before installing Target. Should be ok now. (It can also be due to the Teamspeak 3 joystick plugin. I had to delete it). If you read the ThrustMaster TARGET release note, it is said it is a must. Warning Unplug all T.A.R.G.E.T-compatible controllers before proceeding with installation. When prompted to reboot after installation, plug each controller again. If we install TARGET with controller plugged in, it will take a long time to install filter, and controller will not hide when we run a script. Must reinstall properly after having made this error. Many people do it. As we have to plug our controller to install the driver.. And.. We rarely read release note. ----------------------------------------------------- Another one: What I did to remedy this. 1. Unplug joystick and uninstall Drivers, then TARGET 2 Deleted all Thrustmaster folders in >Program Files, Program files x86, and Users\UserName\AppData\Roaming 3 Went to Device Manager>View> show hidden devices 4 (make sure at this point al your regular USB devices such as phones, printers and headphones are connected to USB) DO NOT CONNECT your Thrustmaster device 5 Right clicked and uninstalled all greyed out Universal Serial Bus controllers, Human Interface Devices. ( for a good measure look through other categories to make sure there isn't a greyed out Thrustmaster device somewhere there) 6 Restarted the PC 7 Plugged in my joystick and let Windows install drivers. I did not install drivers from thrustmeter support downloads. What that changed is that now my joystick is displayed as a Thrustmaster Virtual Game Controller (root) : Status OK. Instead of T.16000m FCS : Status OK. 8 Installed TARGET --------------------------------------------------------- This one above is different because in step 7 and 8 he's plugging in his joystick before installing Target which should not be done according to the release note. --------------------------------------------------------- Also,my own encounter with this problem (at that time with the Target Gui which returns the same error): PS: The solved not 100% points to the device analyzer problem where devices don't show up, nothing to do the internal error. To remove the "USB HID device with hardware ID cannot be found" message when compiled I edited target.tmh and commented out the Thrustmaster devices i don't have (this was not needed on older target.tmh versions). If you can't solve it, you can contact TM support through their website. It can take a few days before they respond but I always got an answer and they go through until you have a solution.

Onboard graphics card on the motherboard? If yes, disable it in the BIOS and be sure to plug the monitor cable in the correct port (that of the RX 9070 XT)

Update to the problem of long script stop times and dragged windows not staying in place after closing and re-opening TARGET. Updating to Windows (11 Pro) 24H2 from 23H2 seems to have solved the problem.

Using the keyboard, the gear goes up and down. But the same happens in other modules, not only in the F-16. If I keep it pressed (keyboard) it just performs one single action, either up or down depending on the state. To rule out an accidental double press I'm using TARGET's PULSE command to only send one single command when a button is pressed. It's not really necessary to do it that way but that's how I set it up. I just tested with the keyboard instead of the Warthog (no TARGET script running) and even with the keyboard the gear just goes up when I press the keyboard and comes down when I press it again.

I don't have that problem (no tinkering with the lua's here). One press the gear goes up, next press it goes down. Never a double action. Only testen F-16 as i don't have the F-4

It resides under the UI Layer: Names have changed over time... null

Must be something on your end because I don't see that when running your track.

Can't comment on the brand but 32GB is an absolute minimum these days. DCS uses up more than 50GB on the CW Germany map... It will not take long before 64GB will be the minimum.

Which driver version? I'm currently on 576.28

Works for me. What does not work with preset K?

Reset trim before take-off...

It's a RAZBAM module and they are not available right now due to a dispute between RAZBAM and ED.

CW Germany map can easily go over 50GB RAM with not much going on so....

Fill me in because the content is blocked (user tracking across sites and or advertising).

Pixelation like this comes from using DLSS which also creates ghosting. No pixel issue when using MSAA but then there's more shimmering.

If it doesn't work or partially doesn't work a few times it isn't a full proof solution. No need to wait a few days. It's not that i wait until Friday that it will change from working sometimes into always.

Reacted a bit to early I guess. Came from a multiplayer session, ended the game and exited was greeted with a 30 sec black screen on exit. Because of that, restarted DCS, selected a single player mission, loaded it, quit and exit... again that 30 sec black screen. Checked autoexec.cfg, bkg_load_signed_plugins = false still in place...

Works fine...