Target woes on new Rig.
-
Its not a rights or compatibility issue. One of the first things checked.
Its not a keyfile, Target user created script or .fcf problem either. (created empty items)
It has something to do virtualization.
My Logitech G900 also uses virtual devices, that’s the next item to eliminate. It’s also a recent addition.
-
Its not a rights or compatibility issue. One of the first things checked.
Its not a keyfile, Target user created script or .fcf problem either. (created empty items)
It has something to do virtualization.
My Logitech G900 also uses virtual devices, that’s the next item to eliminate. It’s also a recent addition.
Well damn, I had the exact same problem. I remember getting that same filter error. Once it’s solved, we will remember forever next time…
-
I’m still on Win7 , and this might be part of the problem as it is officially only supported by Win10.
It certainly is NOT an issue of running it on Win 7 as I am also still running Win 7 and using TARGET version 3.0.16.615 and I am not having that virtualization problem at all. I always run installers as admin so the install can go smoothly but I do not run TARGET as admin even if doing so might be best practice and it works fine for me.
-
Win7 should be the best at this. It’s Win10 that increased my number of problems with TARGET.
This is what my output log shows when I run with TS3 active. I get:
Running script: B:\Desktop\Gaming Support\Combat Flight Sim Aux\TARGET\DuckBMSv7.tmc *** Allocated ProcInstances found from the previous run: use FreeProcInstance() *** 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[2]: 1: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100" 2: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100" ```which hangs for ~5 seconds and completes with
USB HID device “Throttle - HOTAS Warthog”(USB\VID_044F&PID_0404\8&1BECBDEA&0&4) selected
USB HID device with hardware id “VID_044F&PID_b351” cannot be found
USB HID device with hardware id “VID_044F&PID_b352” cannot be found
USB HID device with hardware id “VID_044F&PID_0400” cannot be found
USB HID device with hardware id “VID_044F&PID_B10A” cannot be found
USB HID device with hardware id “VID_044F&PID_B10B” cannot be found
USB HID device with hardware id “VID_044F&PID_B687” cannot be found
USB HID device with hardware id “VID_044F&PID_B679” cannot be found
Virtual HID devices managed by script!
Connecting virtual joystick…Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard…Done
Connecting virtual mouse (absolute axes)…Donemain returned 0
On the other hand if I run without TS3 running I get:
*** Allocated ProcInstances found from the previous run: use FreeProcInstance() ***
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[2]:
1: “Joystick - HOTAS Warthog” - “USB\VID_044F&PID_0402&REV_0100”
2: “Throttle - HOTAS Warthog” - “USB\VID_044F&PID_0404&REV_0100”
USB HID device “Throttle - HOTAS Warthog”(USB\VID_044F&PID_0404\8&1BECBDEA&0&4) selected
USB HID device with hardware id “VID_044F&PID_b351” cannot be found
USB HID device with hardware id “VID_044F&PID_b352” cannot be found
USB HID device with hardware id “VID_044F&PID_0400” cannot be found
USB HID device with hardware id “VID_044F&PID_B10A” cannot be found
USB HID device with hardware id “VID_044F&PID_B10B” cannot be found
USB HID device with hardware id “VID_044F&PID_B687” cannot be found
USB HID device with hardware id “VID_044F&PID_B679” cannot be found
Virtual HID devices managed by script!
Connecting virtual joystick…Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard…Done
Connecting virtual mouse (absolute axes)…Donemain returned 0
I wonder how that compares to your experience. Does it hesitate in the same spot with the same kind of output text or not?
-
@ Stubbies: This Ryzen CPU and its motherboard is “NOT Officially SUPPORTED” by Win7 as I mentioned in an earlier post. For that matter neither is the new Intel line of products.
I have already trialed Installing Win7 at least 3 times with different strategies of applying as many Microsoft updates as possible before they lock me out.
Each time there are different issues and/or inconsistencies. The last install I had some CPU throttling working while OCing but this time none. (example)
Another is while installing Win7 there is no USB support and I have to use a PS2 keyboard to navigate.@ Fred: It only throws up an error on Targets initial run or if I move the Stick/Throttle to a different USB controller.
After that it just pauses for 5sec or so before it finds the devices.
-
@ Stubbies: This Ryzen CPU and its motherboard is “NOT Officially SUPPORTED” by Win7 as I mentioned in an earlier post. For that matter neither is the new Intel line of products.
Which means Kaby Lake and newer Intel CPUs which you are 100% correct on.
I have already trialed Installing Win7 at least 3 times with different strategies of applying as many Microsoft updates as possible before they lock me out.
Hrm one thing I just thought about now how to possibly get partially around this is have you tried a slip streamed install of Windows 7? It wouldn’t bypass the lack of ability to use windows update directly so if you wanted to keep updating it would force a really clunky updating of the slip streamed install and forced re-install of Windows 7 but I think it would work.
Each time there are different issues and/or inconsistencies. The last install I had some CPU throttling working while OCing but this time none. (example)
Couldn’t tell you about that one. MS isn’t going to be doing anything to make sure Ryzen actually works with 7 so it is a definite YMMV situation.
Another is while installing Win7 there is no USB support and I have to use a PS2 keyboard to navigate.
Actually this statement isn’t fully correct. Of course Windows has USB support built in. What it doesn’t have built in is USB 3.0 and newer support and I’m willing to bet your mouse was on a USB 3.0 connection hence your problem. This is alleviated by slip streamed installing.
-
Which means Kaby Lake and newer Intel CPUs which you are 100% correct on.
Correct……Though Intel has a closer relationship with MS. But I didn’t go Intel again, back to AMD this season.
Hrm one thing I just thought about now how to possibly get partially around this is have you tried a slip streamed install of Windows 7? It wouldn’t bypass the lack of ability to use windows update directly so if you wanted to keep updating it would force a really clunky updating of the slip streamed install and forced re-install of Windows 7 but I think it would work.
Have no idea what a “slip streamed install of Windows 7” is. But I did hear you could change from a legacy bios to a UFEI with out reinstalling Windows !
As soon as I have the spare cash i’ll go Win10Couldn’t tell you about that one. MS isn’t going to be doing anything to make sure Ryzen actually works with 7 so it is a definite YMMV situation.
That’s OK I,m good. While AMDs Ryzen I believe to be a mostly new CPU, Intel has done little to their Line.
Actually this statement isn’t fully correct. Of course Windows has USB support built in. What it doesn’t have built in is USB 3.0 and newer support and I’m willing to bet your mouse was on a USB 3.0 connection hence your problem. This is alleviated by slip streamed installing.
Well Stubbies this statement is correct. And I say this cause I have actual/real experience with this circumstance on this Motherboard.
Would you like me to expand on this, , I thought you would.
Simply stated, In the bios setup I have USB keyboard AND mouse support, but as soon as I start Win7 setup I lose all access to these input devices.
HOWEVER I can still use a PS2 keyboard. and hence install windows to the point where I run the “motherboard chipset drivers” then I have USB.All three USB controllers are native USB3 devices and have backward compatibility after Driver install. Well thats how It works out.
I just didn’t have any USB regardless what you might pothesize.
-
Correct……Though Intel has a closer relationship with MS. But I didn’t go Intel again, back to AMD this season.
Well that and MS is supporting Sky Lake fully until Win 7 EOL and Kaby Lake is hardly any different than Sky Lake so a big time advantage for Kaby Lake users that want to still push Win 7. Since Ryzen didn’t have a direct predecessor build wise you are definitely bound to run into more Win 7 issues.
Have no idea what a “slip streamed install of Windows 7” is. But I did hear you could change from a legacy bios to a UFEI with out reinstalling Windows !
As soon as I have the spare cash i’ll go Win10A slip streamed install of Windows is one where you have patches pre-installed into the Windows installer. This helps out a ton on Windows 7 since the Windows Updater was notorious for hanging forever trying to even get a list of what needed to be updated with a clean install of Windows 7. After I built my slip streamed install of Windows 7 and installed it I only had like 15-20 updates to do to be current on my last re-install versus the hundreds that would have been in the list with a standard Windows 7 SP 1 install disc. Most of those 15-20 were motherboard/hardware specific updates and not Windows 7 updates. It takes awhile to make the initial build of the install but once built most of the work is done forever. You would only need to add in patches if you wanted that released post slip stream build.
The down side/up side to doing it this way is that, of course, the Windows installer gets huge compared to original so you must use either a blu ray disc or a USB thumb drive to hold the files as a DVD isn’t nearly big enough.
That’s OK I,m good. While AMDs Ryzen I believe to be a mostly new CPU, Intel has done little to their Line.
Yup. This is the down side to lack of competition from AMD for so long. Intel got lazy.
Well Stubbies this statement is correct. And I say this cause I have actual/real experience with this circumstance on this Motherboard.
Would you like me to expand on this, , I thought you would.
Simply stated, In the bios setup I have USB keyboard AND mouse support, but as soon as I start Win7 setup I lose all access to these input devices.
HOWEVER I can still use a PS2 keyboard. and hence install windows to the point where I run the “motherboard chipset drivers” then I have USB.All three USB controllers are native USB3 devices and have backward compatibility after Driver install. Well thats how It works out.
I just didn’t have any USB regardless what you might pothesize.
With a slip streamed installer of Windows 7 the USB 3.0 patch is built into the basic Windows installer so it knows how to handle USB 3.0 versus any standard Windows 7 SP 1 install disc that were built prior to USB 3.0 ever existing. The slip streamed install having the patch already there it knows how to deal with the hardware so you can use it for mouse/keyboard on a USB 3.0 connection.
For anyone that has worked with Windows for a long time this shouldn’t be surprising at all. I remember having to install network drivers on older Windows 95/98 installs so I could use the NIC or the NIC built into the motherboard for internet access.
-
Ah yes now I’m with you, (its morning & i’m sober, relatively) I had forgotten the term, but did know it was an option. However I needed a functional install first to setup the Disc with USB drivers and Updates.
This all takes time. And I first have had to learn what the issues were going to be with this particular combination of hardware.
I still have a box somewhere full of Boot floppies with various Nic drivers for Client machines and others with File managers included. Those were the days. Its surprising how quick I forget, or move on might be a better term.
And as I intend to go Win 10 as soon as I have the spare cash, I am persevering. Or trying too. If I can.
-
Hi Shad!
-
Ah yes now I’m with you, (its morning & i’m sober, relatively) I had forgotten the term, but did know it was an option. However I needed a functional install first to setup the Disc with USB drivers and Updates.
It was all in planning for the Windows refresh for me. I knew I was overdue for a clean Windows 7 reinstall so I set up the slip streamed install USB prior to killing my current install so there were no issues or surprises.
I still have a box somewhere full of Boot floppies with various Nic drivers for Client machines and others with File managers included. Those were the days. Its surprising how quick I forget, or move on might be a better term.
Well we did go a very long time without having to deal with those issues so the just sort of faded away in memory. It wasn’t until the whole USB 3.0 deal and Windows 7 that I even remembered about it.
And as I intend to go Win 10 as soon as I have the spare cash, I am persevering. Or trying too. If I can.
Yeah with a Win 10 install disc USB 3.0 support won’t be an issue. Win 10 has it’s own issues which is why I have chosen to remain on Win 7 but I totally understand running Win 10 on a Ryzen system or even a Kaby Lake setup as it would be a PITA to keep the computer current using the slip streamed method.
-
SMOKING GUN found.
Teamspeak3 is the offender here.
I’ll need to do some thorougher testing tomorrow. But for now its applying the filter as it should.
Thanks Fred
Post back latter.
-
And the saga continues.
Now I have lost MFDE functionality. Instruments and MFDs.
This morning they started working again but not latter in the day.
And Target was able to hide the Stick & Throttle and present a Combined Device OK while TS3 was running.
Tomorrow I get hit by a truck while going to church. I don’t expect any solutions, but do sent flowers.
I will be doing a OS Reinstall again soon.
-
@Shadow I am so sorry to hear this, keep on!
@all FYI: I am talking with TM Tech Support, once I am finished I will share with you the entire thread.
-
Dude, you have too many , or at least some problematic (virtual-?)input device driver, filter … at least not compatible with TM input driver/filter. eg. TS3’s filter … it has input driver so can be controlled by mouse or stick buttons.
And that is your problem. You need to uninstall / un-register all filters that use some input (virtual) devices … , well at least ones that you don’t need for the time when configuring your real inputs.
Maybe even some china-mouse driver…So 'regsvr32 -u name.dll" of that filter’s dll.(it is very likely that are .dll’s, .ax are multimedia codec files, but still use regsvr32) … but write them down , or make a batch script. … So , any INPUT filter that you know it is not used for TM configuring , eg TS3’s dll but that is solved,
Now you have to search which ones you have installed and are registered in dll’s table… there are even softs for right-click and -register/unregister.You see how you’ve re-discovered TS3 problem, answer was in the 4th post…, when sober
Good luck.