MadMonty

Use OpenXR-API-Layer-tool and check if MBQV is ticked

Please pay attention, that after updating PP MB Quadview is deactivated. I had stutters too, checked status of MB QV, activated it and everything is running smooth again…

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. Thank you very much. Worked all night to solve the problem. At the end I asked ChatGPT and went through all steps, incl. deactivating all other USBs, connecting throttle directly to PC and deactivating MSI afterburner and a couple of other software. Script was moved to TM folder in C:\Programme\TM\Scripts... At the end, I managed to get the driver installed and TM Throttle running als TM combined with DX buttons. Very much relieved now...

Hi! I defenitely need some help here. Have been using Thrustmaster Combined Full DX Mapping for years without a problem. Now I have updated Win11 to 22H2 update and everything is messed up. Couldn´t use it anymore, had compile errors. So I downloaded latest TARGET and V2.7 of Full DX Mapping, but no joy. I always get the following error: Running script: F:\UPDATE\Thrustmaster\TARGET Profiles\TM_Combined_Full_DX_v2.7\TM Combined Full DX\Run_Simple.tmc Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll" Compile Succeeded. Physical USB HID devices managed by script! Currently plugged USB HID devices[3]: 1: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100" 2: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100" 3: "T-Pendular-Rudder" - "USB\VID_044F&PID_B68F&REV_0110" Error:(internal) cannot associate a filter with the selected USB HID device "VID_044F&PID_0404" USB HID device with hardware id "VID_044F&PID_0416" cannot be found USB HID device with hardware id "VID_044F&PID_0417" cannot be found USB HID device with hardware id "VID_044F&PID_0438" cannot be found USB HID device with hardware id "VID_044F&PID_0439" cannot be found USB HID device with hardware id "VID_044F&PID_0432" cannot be found USB HID device with hardware id "VID_044F&PID_043A" cannot be found USB HID device with hardware id "VID_044F&PID_0420" cannot be found USB HID device with hardware id "VID_044F&PID_0428" cannot be found USB HID device with hardware id "VID_044F&PID_0421" cannot be found USB HID device with hardware id "VID_044F&PID_0429" cannot be found USB HID device with hardware id "VID_044F&PID_0422" cannot be found USB HID device with hardware id "VID_044F&PID_042A" cannot be found USB HID device with hardware id "VID_044F&PID_041B" cannot be found USB HID device with hardware id "VID_044F&PID_041C" cannot be found Virtual HID devices managed by script! Connecting virtual joystick...Done Device name set to Thrustmaster Combined main returned 0 already tried the following: Open REGEDIT (Windows + R; Type "regedit" and run it). Go to this, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB Then look for the following; VID_044F&PID_0404 You will then use the drop-down menu to open and find Device Parameters. (Clicking on Properties will not work) Off to the right, Every number that you see (#) like that, we are going to change them all to (0). Do not leave any 1's behind. Restart and Enjoy. Also reinstalled drivers and reinstalled TARGET, having switched off TM USB devices. But still I return to the above error message. Any ideas??

Dear @Calvin.Pimax, any news about the planned update...? Are we still on course for an update today (or tomorrow)? Thanks!

there is a permanent solution:

With my Pimax Super it helped to set the max FPS in DCS to 120 (not higher) to get rid of micro stutters.

Dear @Calvin.Pimax, could you please give the community an update on when we can expect the next version of Pimax Play? Currently, many Super users like me are still experiencing some problems with the headset (especially at night and with tracking), and we are naturally hoping for a significant improvement in the next PP version. I'm asking because it's become suspiciously quiet on the software news front. Last but not least, when will the lighthouse faceplate be available for the Super? Thanks!

It´s not a bug, I had the same problem. They have integrated a new setting in the menu. Look in your settings and tick "Controllerless mode"

Try rolling back to the version before, I haven´t made the last update on Sept 10th

Are you guys using latest NVidia drivers? Have read about troubles and therefore did not update from the penultimate one

Good hint is to use passthrough (just double tab the headset to switch to passthrough) and watch if any light sources are flickering. If so, shut them off, cover them or try to reduce lighting until you don´t see a flickering. My room was way too bright at the beginning and I had to reduce the light sources.

1.42.1 PP (latest version) and the latest firmware, which comes with 1.42.1 (being in office, not nowing the firmware number)

Look at my report regarding tracking…

No shut downs on my side… Keep fingers crossed it stays that way!

No, works just perfect. Even with Necksafer. Everything is fine from my point of view… Only night visuals remain a problem no matter what PP version.

1.42.1works with M-QV, you might have to reinstall M-QV after Pimax update. 1.41.1 had troubles with M-QV, but that has been resolved with a hotfix for PP (happend before the later release of current 1.42.1)

Oh boy - I already lost faith for the so needed pilot body for the A10C II. Now you reminded me on something I have nearly forgotten after so many years. Makes me kind of sad…

Are you using the OpenXR API Layers GUI tool according to Tallys Video? If so, please have a look that Necksafer is on #1 in the ranking (before QV). In my case, that resolved the problem with Necksafer. And also deactivate Eye Tracking in DCS when using Necksafer.

Here we go.... Running QV via QV companion and everything according to Tallys video PS: Hope you don´t mind the settings in German language!

Yes, QV leads to the grey veal ("white box"). But - in my case turning off SSAO while using QV solved the problem. Had a thread regarding this issue a couple of weeks ago:

try turning SSAO in DCS OFF

Honestly - I don‘t know. But since all of us have night visibility problems, I don‘t think it is hardware related, since the displays should be capable of showing black without halo and the other stuff… As you see, the problem with sunrise/clouds can already be solved by settings in the software. Maybe Pimax / Calvin can make a statement here…

I’ve updated my original post to include the issues with the Pimax during night missions – it’s not quite perfect after all.

Hey guys - quick update... I have now extensively tested the issues and adjustment options in a night mission (Syria, June, 4 a.m.) and a dawn mission (Syria, June, 04:15–04:30 a.m.): Problems: HALO around bright objects, especially the aircraft in external view Indefinable dark mass from the horizon downward; the transition from the stars over the horizon to the ground is not a clear line, but a constantly shifting “something” Partial “blackout”: when rotating the external view of the jet, brightness suddenly dims completely (across everything); when I then switch into the cockpit, everything is pitch black and the headset gradually brightens again Chromatic Aberration at sunrise / clouds, as described at the beginning of the thread Adjustment options: Contrast & Brightness in PP Local Dimming in PP Gamma in DCS Modifying the profile.json file as described by missioncmdr Upfront, everything that doesn’t work or has no effect: Problems: HALO does not go away, no matter what I do Horizon-to-ground transition remains undefinable Blackouts are still present Adjustment options: 2. Local Dimming in PP makes no difference 4. Modifying the profile.json (simply adding the line with the value, as it is not there initially) causes changes, but in my view nothing that Brightness couldn’t also achieve The only progress so far: Problem: 4. The Chromatic Aberration at sunrise or sunset on the horizon and in the clouds can be removed. Workaround: Set Brightness in PP to -2 and Gamma (previously 1.8 for me) to 2.8 (!). This results in beautifully smooth transitions without artifacts. I tried calibrating the correct brightness against the stars: everything I can see at B=0 and G=1.8, I can also see again at B=-2 and G=2.8. The problem then is with daytime missions: here, with B=-2, Gamma needs to be set to about 2.2–2.4, otherwise it looks too bright. You can fine-tune this a bit by setting Contrast to -2. Then Gamma can stay at 2.8 without affecting nighttime visuals, and during the day you get roughly the same brightness, although the colors appear a little more muted. On the other hand, Gamma can be changed during flight (for day/night missions). So – currently I’m using: In PP: Brightness -2 Contrast -2 In DCS: Gamma 2.8 Fun fact: If Pimax Play is completely closed and restarted, you still get the Chromatic Aberration despite Brightness -2 and Gamma 2.8. I need to briefly move the Brightness slider in PP, set it back to -2, hit Apply, and then the setting works again. This seems to be another bug. @Calvin.Pimax – please have your team take a look at this. It should all be solvable!