bn880

Great mission (really brilliant), but the trigger spawning magical AH64's near "Dallas Warn Zone" (N42 47.3 E43 25.7) FARP are just unrealistic and annoying. I flew in there twice via the valley where they spawn towards the FARP, only to have them on my butt 3 minutes later. This is breaking all kinds of laws of reality. If you're going to send in magical AH64's, at least please do it from an actual FARP/airbase. Edit: All the defense activated aircraft should be spawning from appropriate bases, OR at least very far away to make up for that. Otherwise it just breaks immersion and any kind of proper tactics.

Another advantage of using TARGET though is you can swap your profile mid game to another aircraft and fly that without restarting DCS. (but yes, it is a bit of a pain to set up initially)

http://www.shoprbc.com/ca/shop/product_details.php?pid=88764 they don't stock it though, it could be a 1 to 20 weeks wait until it ships from supplier. http://www.amazon.ca/dp/B00371R8P4/ref=asc_df_B00371R8P43230721?smid=A3DWYIK6Y9EEQB&linkCode=df0&creative=395381&creativeASIN=B00371R8P4 1-3 month ship delay http://www.1c2c.com/ecuisp/~1c2c/lec/plugin/index/framePage.jsp?location=../product/productDetail.jsp?productId=895419&utm_medium=cpc&utm_campaign=january%2B2012 Same

2nd PCB arrived, seemingly identical as last time from 2010 with FW 20. Installed, everything seems to be working great again in all ports/HUB's. (flashed to FW 23 to be safe) However I think I will no longer take the risk of using the throttle in a USB HUB. Direct connect only (not great for those setting up extensive pits)

My throttle 13908 fried 2 days ago again on USB 3.0, still works on USB 2.0. That's twice in 2 years. Still on warranty so crossing fingers that I get another PCB. It gets into bulk mode, but can't be flashed in bulk. It can be normally flashed but that doesn't resolve the issue. Fun.

That's why he kept them off. :megalol: Or: Who can afford clothes after the price tag on the Hog. Good tip with the sanding, might try it someday (sounds like it will help)

Yes very bad news, wish him all the best. I'm a Schumi fan myself, but I have to say that in life you have to realize when you've used up all your luck and limit the dangerous stuff. (basically taken enough risk) Very good that he wore a helmet, even if most of those helmets are not very good for high speed crashes. (they are worse than cycling helmets for example) In any case, if you do very risky sports, you'd better take all the safety precautions. I had a helmet save me just this year on an MTB. (just wish I had knee pads, wear them now)

I use them to indicate which layer (of the 6) that I'm in. As I have different aircraft set up under each layer.

To avoid bricking your warthog connect it when the system is booted up, and disconnect it before shutting down. (apparently not following this or a power outage bricked my throttle where it required new parts) The USB port speed should not matter. Also I have seen some small pattern that suggests it is a bad idea to disconnect the warthog when a script/profile is running on it. So stop any scripts first. (I had my stick brick like this, but it was flashable and recoverable) You get no real benefit from connecting stick/throttle to USB3 AFAIK.

Check to make sure that the devices don't have some warnings on them under their properties. There may be error messages even if you see the icons in Control panel. :/

Was having some stuttering in MP as well, and what I perceived to be lower framerates. (only tried 1.2.7 briefly) Certainly seems more resource intensive than 1.2.6. (perhaps because it's alpha) ka50, low to the ground stuff (so may be related to UH1)

Yeah, tis down here as well.

This changelog looks very promising. Debugging capability (recordings), stability fixes, Increased HE range etc... great stuff! I also like the order of things, having stability right at the very top says indirectly that ED is taking this seriously. :)

Yes a lot of the toggle switches are not possible to break apart AFAIK. For some things you might be able to devise clever key press sequences to imitate different positions. (like for flap positions)

^ So I received the replacement PCB from TM. Identical 2010 board and CY8C24894-24L PSOC. Firmware 20. After a quick install I'm OPER again. TM states that to avoid the issue its best to plug in the throttle after windows load, and unplug before shutdown. In any case, after warranty expires, it should be easy to order a replacement part through them, it should be quite cheap.

I know what you are saying, but IMO this isn't a good compromise. The AI should be looked into instead of a mismatch between your Launch Auth, Fantas/HUD feedback and RWR. I know DEAD is to easy, SEAD is not really simulated, but just a strange way to detonate your missiles when you've got all your ducks in a row is not the best answer. :/

Lets hope this bug gets a fix then :)

If you look at the pic I posted above, it's the left-most switch, I count 7 wires.

Look for extra solder under the connectors for the wires. Mine was shorting the switches in the right throttle like that straight out of the factory. What you need to do basically is A) check that all the wires have a connection between the coolie hat and the right throttle board. B) check the same for the harness that goes from right throttle board to the throttle main board C) check for extra solder under the connectors for the above. if all this fails, you have a burned IO chip somewhere or bad soldering not making a contact.

Bricked. Mine just bricked. Was using it through a Pluggable USB3 hub. Connected to a Clevo P170em board. It seems to have lost it's firmware bootloader, only 4 bytes are recoverable with the TM software and very rarely at that. The Throttle can still work on some ports like through a Dell monitor, but not most others. (I think this has to do with a signature saved in windows for the controller on those ports) So... tried re-flashing it a few times, still not fixing the boot loader/ID.... spent ONE HOUR on hold trying to reach the Canadian support line of Thrust Master today while I was troubleshooting. Until it was game over.... (too late) Hoping that I can get TM to send me a board once i do finally reach someone. Edit: I had it running Firmware 20 for about a year. Edit2: After going through a small troubleshooting dance with TM support via email, they agreed to send me a replacement PCB for the throttle. So this sounds very good in my case. Hoping the new board is much more resilient.

Had the same error today, was flying an Su25t, happened when i: - started in unarmed su25t on ramp - requested rearming of custom loadout - turned on electronic power - shut OFF left engine (even though engines were already off obviously) - boom, crash. happened a few times in a row when i retried. then it stopped happening.

Yeah I just experienced the same on 104th server. Most exploded infront of my face when the Radar emitters stayed on etc. Nothing ended up hitting. It was one of those attack(Blue) vs defense(Red) missions, not sure if it's something with the mission or the Sim, but in any case, 2 words: backwards compatibility.

Ouch, I just noticed this today. Not so nice, had some really cool emergency landings I wanted to video capture... :( (Using 1.2.5 to play back old replays.)

Dx is just an acronym for DirectX (referring to Microsoft's Direct Input library)

Cool, yeah BTW that's exactly what happens in the profile I uploaded as well. By default all the stuff is assigned a DX ID, so when you don't see a button in the script, it's automatically acting like DX. :) I guess we were trying to solve the same problem and that's the result