Deezle

Supposedly it was nearly done when the Viggen was first released, yet here we are... From 1-22-17.

Don't listen to the entitled among us. Many of us have figured out and enjoyed Ikarus without trouble. It's an essential part of my flying experience :thumbup: If you had a donation page I'd send a few bucks your way.

I too have had a couple weird problems with my right toe brake that I haven't been able to nail down, but it hasn't been a persistent thing.

I was actually wondering a couple days ago if anyone ever solved the i2c problem for the WH slew. I'm very curios about the circuit.

That will come at some point during the Hornet's development.

You can do that, but you also waste an input you could use for something else. If I used switches that had on positions for every switch position I'd double the amount of inputs I'd need and I'd run out of existing inputs to wire them to.

Deferred shading in 2.2 definitely altered how the MFCDs look. If you export the the screens to a monitor the affect isn't there, or you can turn off deferred shading.

The problem with what you're trying to do IIRC, is the Huey is one of the modules that also has a lua for the TMWH. You need to add the command you want to that file, else it will not be mappable to the TMWH. You can also just delete the TMWH lua file, but it will reappear after every update.

A big problem is you cant just plop it on a desk like most users do with a throttle. The end user needs to figure out how to mount it alongside their chair themselves. So from that perspective it complicates what a company can just sell and hope their users can make work for themselves.

I prefer a center stick. Also easier to take over with your left hand if you need to use your right hand for something (such as the mouse in the sim world).

Also having a cockpit myself (although nowhere near OP's level), it wasn't very practical in VR. There's nothing wrong with a nice display.

Looks awesome! This is normal (maybe joy2key allows you to change this, I've never used it) Now you have to edit some lua files for the modules to properly use your toggle switch inputs. It's time consuming but worth it. I made a tutorial thread/video, you can find others as well. https://forums.eagle.ru/showthread.php?t=186695

Thanks for the help! I look forward to using the latest version.

Those aren't tanks. The problem with the GAU-8 isn't power, it's that the dispersion appears to be too high.

Windows 7 Pro 64bit.

Derek Speare boards can do a lot. You need two inputs per encoder, so 16 on the 32 input board or 32 on the 64 input board.

Correct.

I have a separate D: hard drive. I tried saving a profile there, same problem. I tried moving the entire Ikarus folder there, same problem. Ikarus does not give me any error messages that I'm aware of. Wish I would have kept a copy of the previous version. I figured out how to download a previous version from Github, I downloaded 1.2.1.3f and it works fine.

Auto lase works fine in 2.2. I'd suggest reviewing your procedures.

Above you said I need to try saving the profile to a different folder, I tried a couple different folders with no joy. Apparently I'm not the only one with this problem. Ikarus worked fine until I updated. I don't know what more you need. Just downloaded it again. I opened a profile, changed something, attempted to save the profile and I get "Ikarus has stopped working". Does this help? Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: Ikarus.exe Problem Signature 02: 1.2.1.5 Problem Signature 03: 5a3d296e Problem Signature 04: System.Data Problem Signature 05: 4.6.1590.0 Problem Signature 06: 5787f01e Problem Signature 07: 1103 Problem Signature 08: 39 Problem Signature 09: System.IndexOutOfRangeException OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: d254 Additional Information 2: d254dc5bd951bfb0cecba21c69f6f756 Additional Information 3: 55c7 Additional Information 4: 55c7a175b77d03a7c2254f1f59f7fff1 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt

Still crashes if I attempt to save to a different folder.

The switch action you're looking for is ON-OFF-(ON). The parentheses around the second "ON" indicate that position is momentary.

Turn the TGP on. Select A-G when it's warmed up, hit CTRL (OSB 1) and you'll have laser and LSS codes on the left side, type the desired code into the scratchpad and hit the corresponding OSB to change the value. Changing the bomb codes is more involved but those should always be 1688 at mission start but the TGP codes can be different if the mission builder puts extra effort into it.

First confirm your laser is firing. One of the most common errors is creating an auto lasing profile and then deselecting that profile, and then simply selecting the bombs again on the DSMS. If you do this, you're selecting the default weapon profile and it will not automatically lase. I find it easier to manually lase instead of having to select the correct profile. Are you using someone else's mission? I've found with the NTTR mission created by the 476th, the planes have a different laser code than the default 1688 that the bombs are always set at on mission start, this threw me off the first time I used the mission.

Do you happen to be using SimShaker? I found my SimShaker and Helios did not play nice together, however Ikarus works just fine.