anlq

Hi all, I notice MiG-15 trim is limited above 900 km/h. The aircraft tends to climb above this speed no matter what I do. Is this a bug or a ... feature, can anyone confirm ? I'm using TM warthog with G27 pedal. Thanks you.

Those 2.5 screenshots are very nice. But someone please tell us if there will be more hardware demand on this ? Do we need to upgrade hardware for the new 2.5 ?

No sir, no TM fast service is found Thank you for your kindness. I managed to find Target 1.0 but it's still the same. :cry:

It has been 4 days and I haven't got any final answer. I found many thread/post related to software malfunction, it seems target is not reliable. After digging more about the bug using Dependency Walker (a debug tool), it came up with an announce of irrelevent CPU/Account something. My head is spinning right now :mad: :huh:

This doesn't work. I contacted someone on the Facebook page of Thrustmaster, he answered that I have to install with Administrative account. The fact is this is my home PC, so Im using only admin account. I tried many ways like disabling Anti-virus, run in compability mode, reinstall .NET framework. The weird thing is Target installation os always successfully, but then no Tmservice or FAST something is found on services.msc. :doh: Reinstall windows is the last solution I want to do.

OK I'll post their answer here. I found this solution, maybe I'll try when I get home, now I'm at work. http://forums.eagle.ru/showpost.php?p=1825789&postcount=6

It's still the same error. I tried removing saitek driver (old X-52 pro joystick) and enabling xHCI in BIOS (I had to disable to turn off usb 3.0 which is not friendly to Saitek X-52 pro). I sent message to Target developer, I hope they'll have answer soon.

I did as instruction, installing this shouldn't be a problem. I tried this also. Stick and throttle are now working normally, except Target. :doh:

Yes, I installed Warthog driver before installing Target.

I just got my new TM warthog and trying to install Target, after finish installing I opened the software and got this error, I try asking google but no similar error mentioned. Anyone has the same error plz help me out ? :( I tried to execute with compatibility mode and administrative privilege but no luck

Still no hope for fixing this bug. Hmmmm.

I have stopped playing DCS since last week, come here and I feel dissappointed again seeing the trimming problem still remains. Don't know what to say now. Switching to racing for a while is an only option. See you guys next week.

DCS now is not forcefeedback friendly. Devices with FFB causes trim stop to work in most of birds, and an user reported new update causes lag on his TM warthog. This is a nightmare for FFB user (im using a G27 as pedals now).

I've just downloaded and run some test on the new patch, this trim thing still hasn't been fixed since last month. Trim doesn't work even with Alt+J trick anymore. This must be a very tough bug and ridiculous (It seems no one cares about this and want to give an explanation). CC101, Hawk, UH1, Gazelle are now bricked. I'm very disappointed. I guess I'll take a break from DCS and wait for my new TM Warthog to arrive (in 3 weeks).

Has the trim been fixed in the latest update ? I'm downloading update so I haven't known yet.

I ordered a TM Warhog 2 days ago on Prime Day Amazon before knowing this bricked "bug", this scares me seriously because if there's any same thing happens to my joystick, I have to ship all the way back to the US which is 2 weeks to reach (shipping cost is expensive).

FW-190 trim is weird, because everytime I kick the rudder even slightly, it suddenly moves left or right violently, it seems there is a huge deadzone in the center.

It seems something changed in the lastest patch, radar now working better than before. Not losing lock every time enemy notches or beams.

It has been 3 weeks since my last online, can't play in this condition, too many bugs appeared.

- This. - Trim doesn't work for some aircrafts/helos (using force feedback device, G27 for rudder in particular). Alt+J is a temporary solution. - Control indicator doesn't show up in Hawk and CC101. :(

I meant to buy a new one, sir, not a 2nd hand. :music_whistling:Thank again for your offer.

The outdated thing in CH products does get me concerned because 8 bits sensor causes spikes and jumping while aging. I experienced this with the previous joysticks (not X-52 pro), this was not comfortable to deal with. So I guess I'll take something more modern and up-to-dated. I'll go for the TM Warthog. Thank you all for your opinions.

Hi all, I'm looking for a new HOTAS because my old one (X-52 pro) are worn out, can't be used with USB 3.0 and it's 6 years old. Actually it's working normally except having some blinking leds. So I decided to get another one as replacement. I currently pay attention to CH products Fighterstick/Throttle USB. I did some researchs to see this one is highly recommended by gamers because of its durability, plug & play, good software control (some says it lasts for 10-15 years without any flaw). I can afford a much expensive Warthog but there're 2 things I don't like about it: it's A-10c HOTAS replication (I prefer F-16 stick because I'm F-16's fan), and I don't like colorful leds. So is there any CH.P user out there can give me an opinion ? Is there any problem using CH_P with usb 3.0 and Win7-8-10 ? and is there anything you don't like about CH_P ? Thank you for your advise. :joystick:

RAlt+J then RAlt+J again, problem solved. This trim thing is a real pain in the @$$. :mad: Everything had been good until the latest patch came out.:(

I hope they wouldn't be stuck in a coma. :megalol: