Bottom line up front is, don’t try to update firmware on a warthog using USB 3.0 ports.

 

Long story short, had to pick up a cheap laptop at Target with USB 2.0 ports so I could revive my HOTAS. It was a brick for a little bit there.

 

I’ve been dusting things off and testing, but I still feel like I don’t know where to start 🤣

 

On the good news front I tested out CloD Blitz and I was able to run it relatively stable with medium settings. I remembered back in the day we would test with the Black Death .trk and FPS stayed in the 80’s through the heavy graphics sections. I think next step will be to get together with a patient soul who can help me get some initial setup pointers and test the rig in an online flight.

 

S!

Oh yeah,, the old Black Death test.

Say , do you remember IV JG51 Molders from the old days ?

I found out through a few of my own lessons to use 2.0s on my TM Warthog. Though none of mine turned it to a brick.

 

I wonder if that is what happened to Trev?

I think a communication interruption during FW transfer did it. 

 

There's really no reason to update Warthog FW. If it works, it works. 

Fair enough. My takeaway is to not update the firmware. Ever.

I've been using the 3.0 ports with no issues however I have never tried updating the firmware.

I think a communication interruption during FW transfer did it. 

 

There's really no reason to update Warthog FW. If it works, it works. 

 

This is true!

 

I mean, in a very few cases on some devices like motherboard BIOS or a router or whatever, there might be a valid reason to update, if you first carefully read what the changes that are made are for, and if they apply to you at all.  Most of the changes made to firmware apply to only a tiny percentage of users, and to very limited circumstances; and a lot of times the changes fix the issue that they say it does, but can actually break some other aspect that was working fine before.  In today's world, so many people are used to doing software updates automatically that they apply the same logic toward doing firmware updates...which is a very understandable conclusion to come to.

 

So for those unfamiliar with firmware updates, and even if you are, heed Trev's recommendation and "don't fix it if it ain't broke".

 

S!

This is true!

 

I mean, in a very few cases on some devices like motherboard BIOS or a router or whatever, there might be a valid reason to update, if you first carefully read what the changes that are made are for, and if they apply to you at all. Most of the changes made to firmware apply to only a tiny percentage of users, and to very limited circumstances; and a lot of times the changes fix the issue that they say it does, but can actually break some other aspect that was working fine before. In today's world, so many people are used to doing software updates automatically that they apply the same logic toward doing firmware updates...which is a very understandable conclusion to come to.

 

So for those unfamiliar with firmware updates, and even if you are, heed Trev's recommendation and "don't fix it if it ain't broke".

 

S!

Yeah, many times we just update things just to get the pop up to go away. This taught me to look first to the greatest extent possible.

I was definitely updating the FW for no other reason than it was a higher number - like a lemming.

 

Razwald, you’re absolutely right, it works fine to use in USB 3.0, but FW updates can only be done connected to USB 2.0 or by disabling xHCI if your BIOS give you the option.

This post saved me from a headache.

 

My slew button on my Warthog hasn't worked in a couple months. Since I've been getting into modern aircraft not having a slew button is annoying. So in a last ditch effort I updated my firmware, only after I plugged it into a 2.0 slot.

 

I now have my slew button back which will free up 4 inputs for other stuff.

And this is why forums are awesome to have for posterity!