Guppy

Not trying to necro post here, rather keeping things consolidated. Do we have any update regarding this? I understand this is not a simple fix - but just wanted to get an update. Thanks!

Whoa - no need to get offensive. OP had a legit question, be nice.

Introduction to IKARUS has been added to my blog here: https://guppy.home.blog/2019/07/19/intro-to-ikarus/ Also I've completed my ACES II Seat and have made a BUNCH of buttons (click twice to expand and get them aligned vertically):

So the slew stick is absolutely atrocious. But there is an upgrade that is super easy to install. It basically takes a Ps4 ministick and puts it into your WH. This upgrade makes the WH relevant; it's too bad TM went with a terrible solution instead. https://deltasimelectronics.com/

Thrustmaster TPRs - they're absolutely amazing. IMHO they need to be mounted to the floor though. If you can't mount your pedals to the floor then VKB's are the way to go. they push down with your heel on the ground.

This comes down to 2 issues: 1) too fast. 2) engaging NWS Hi and cranking all the way to left/right before slight forward motion is applied. Once you get used to how slow you have to be you will find yourself not having issues.

Are you referring to remapping the trigger or to the OSB PB?

In controls there is no FLIR power switch for OFF / STBY / ON or UP / DOWN for the right console.

I do the bit test simply because it's part of the start up procedure. Not doing it will not cause any issues, but doing it does not slow down your start up sequence by much.

Its a Windows feature, to frustrate the hell out of you. I've had this happen before to me and usually unplugging everything or switching ports has always seemed to help. Make sure your power options are set correctly, too. https://windowsreport.com/windows-10-doesnt-recognize-usb/

Oh man - this is amazing news. Let me know if you need testing done!

Is it plugged directly into the PC or a USB hub? Is the USB hub powered? If it's plugged into a hub I've encountered this with many different devices. Typically unplugging the hub, rebooting and plugging it back in fixes the issue. If it's a powered hub, do the previous as well as unplugging the power cord. If it continues to do it then your hub might be starting to deteriorate. Try a new USB port on the hub or get a new hub altogether. If no hub, try different USB ports.

For those looking to understand more about IKARUS: https://guppy.home.blog/2019/07/19/intro-to-ikarus/

:( That's okay. Any idea on the F14 module? To my knowledge they shouldnt be making drastic changes like ED did with the Hornet. I'm very eager to get my pit configured for it.

I understand that - what I'm saying is if you configured IKARUS to allow for keyboard strokes I could create a button and map it to "i" to turn on the radar. I could put that button onto a newly created f-15c profile in IKARUS that projects onto my touchscreen. The customization is already in IKARUS. I can create a button for the F-15c profile. The problem is I cannot map it to a keyboard stroke. If you enable the ability to map a button press in IKARUS to pushing the letter "i", for example, you would effectively allow folks to build their own custom profiles for those modules that don't offer full fidelity. Think about my F-18c profile I created. I custom made buttons/toggles and placed them where I wanted them. The only difference is instead of IKARUS sending the "DCS ID" for the corresponding switch/button I pushed, it's sending a keyboard command. This would allow additional expansion for some of the other profiles you have created, too. Since most modules have keyboard shortcuts anyway. I'm thinking L-39, etc. Does that make sense?

The functionality of programming keyboard strokes to buttons is 100% needed. I would say to save on development time you don't need to build out each of those into the current pits... but I would say that functionality would enable even more use cases of the software.

Exciting! HJP - if I can offer some input. Also allow IKARUS to map key strokes to buttons; for example LALT+Home to start the engines (or whatever the key combo is). This would allow users to create buttons for FC aircraft like the F-15c. This would offer so much more possibilities than just assuages, but workable UFC controls. This would allow me to build a custom UFC for the F-15c by using the IKARUS software to creates buttons and mapping them to keystrokes that trigger an event in game.

Thanks HJP :) @Warhog; I'm slowly working on a tutorial on how to configure IKARUS for what you're asking for. But in short, yeah you can do exactly that and more.

This is awesome! A little advice, you might want to consider lowering the total height of the front console by 3". As someone with a pit, you'll find considerable head/eye strain if you dont have the monitor line up to a comfortable eye height over time. Your gauges/UFC/DDIs/etc are very important, but even more so is eyes outside the pit. You also do not want to be too far from your monitor either (as an attempt to keep it in a comfortable viewing angle), you'll find it more difficult to spot targets and wish you were closer. Currently, my main monitor is the focal point and the UFC/DDIs are just a small eye glance down.

I still have a bunch of work to do to the ACES II seat, but things are progressing quite nicely. Below are some update photos: https://guppy.home.blog/2019/07/05/getting-there/

@ED Can we PLEASE get a response regarding this? We should not need to build custom curves to fix this.

That was a tongue and cheek comment. Don't get me wrong the T16 is not a bad combo unit; just really is not a HOTAS and not my cup of tea. But you should use what ever makes you happy. Regardless, it's not a resolution issue. It's the programming done between ground/air idles. In the real aircraft there is a "chunk" of space between the aft end of the throttle track and a point in which it actually engages RPMs. This is programmed into the game, so when you move your throttle from aft it does not begin pushing RPMs until a specific point. This makes X% of your throttle useless. Even if it's only 5%, you should be able to use all of your throttle movement. There's no reason why this should be built into the sim when 99% of people don't have real hornet throttle tracks.

When you're in the air and you move your actual throttle, and look down at the throttle in the pit at the same time, you dont notice that it takes like ~20% of real throttle movement to move the in game throttle? I've seen this behavior with all 3 of my throttles: TMWH, VPC T50 and TM TWCS. Maybe the crappier the throttle is the better it works? LOL

I dont understand why we need to use workarounds for this though. I've messed with the curves and it's an absolute pain and often times the curve ends up not being perfectly linear. It should be as simple as 0% idle - 100% full and anything inbetween pushes RPMs. I understand the desire to make a "real" experience, but the HOTAS we use have significantly shorter throws than the real thing. Much like the TDC in the hornet (needing to push down to move it) developers should implement the sim with an understanding of the hardware we use to support it and make casual quality of life changes for us. /shrug

I just want to bump this and see if any one else has any thoughts. I think a lot of people dont realize that you lose a significant amount of throw in your throttle when flying the hornet. If you look down at the throttle in game, begin to move your own throttle, you'll notice you travel about 20% IRL without moving the throttle in game when you're in the air.