Deezle

Ever since I started using SimShaker, I've been sad that I'm unable to use Helios because of some kind of conflict that caused Helios gauges to be very laggy. I can happily say Ikarus works great along side SimShaker :thumbup:

Good stuff, I'm currently using Helios to map my pots to the A-10 lighting controls. I'm curious how you did this, I'm pretty good at adding missing controls but I've struggled with adding missing axes to modules (except the Viggen) even though your method looks just like mine. Unfortunately, 98% of users are content clicking things with mice instead of building panels, so those of us who hate to use our mice must improvise.

My favorite of my shots.

Indeed. It basically doesn't exist now, near as I can tell.

Player Export has now been disabled again and SimShaker is back to not working tonight :huh:

Looks like "Allow Player Export" has now been enabled and SimShaker now works on the server :thumbup:

Unfortunately, it's possible, but you won't like the result. Because of how the sight is implemented, the exported display will dance around your screen when you move your head. Already tried it.

Sure would like to fly helos on the 104th but Simshaker doesn't work, I assume because some sort of export is disabled ont eh server. I assume this isn't going to change any time soon? Once you fly with Simshaker, there's no going back.

John made a bit of an error in his videos, because of the 3 position switch mapping terminology he had the nomenclature wrong. T0 is "unpressed", T1 is first detent (allows slewing), and TV is second detent and makes fixes.

Back on topic, I too have experienced the sidewinder launching while dropping the BK90.

Same here.

Yeah, MLWS is still not working against MANPADS.

I've also noticed I keep picking up SAM sites when I'm well behind HUGE mountains.

Pots are generally noisy. Ideally ED should address this by allowing some filtering on the axes, like plenty of other games can do.

Radar works great exported, the EP-13 does not (moves around your screen when you move your head). See this thread. https://forums.eagle.ru/showthread.php?t=181656

Aware, but I'd prefer a physical stop.

Because the Mig Radar init.lua file has the export line already in it and the Viggen doesn't.

I found 4" was too long for my taste and cut it down to 3" (7.5cm). IMO the gimbal has way too much angular movement for a much longer stick to feel right, the throw ends up getting kind of ridiculous.

:thumbup::D

I'm fairly confident the left/right mappings for the dials are coming, there's even at least one in the default.lua that's commented out at the moment, I enabled it but it has no function yet, so don't fret, I'm sure they're coming. As well as the various axis controls, which are currently usable by adding them to the defualt.lua.

Well, finally I figured out to export the kneeboard to a viewport, apparently the "try_find_assigned_viewport("xxxxx")" wants to be in a specific portion of the file, not just at the very end where I usually put it. Thanks to this post here https://forums.eagle.ru/showpost.php?p=2278817&postcount=3

6-8nm seems to be pretty common in the A-10, I don't recall ever reaching 10nm. Translates to 11-14km

Viggen effects are working great for me. I know it's a long shot, but it would be pretty neat if it could simulate compressor stalls, would be useful for the F-14 in the future too.

Normally I don't care about the kneeboard very much, but seeing how the the QFE at the target is mandatory in the Viggen, I thought I'd bring this up. With a 4 monitor setup in a "T"-Configuration, only the top half of the kneeboard is visible on the left monitor. I've poked around in the init.lua file trying to change it or export it like I did with the radar, ect, but I've had no luck. The kneeboard builder app doesn't seem to work either like it does with other modules. I'd really love to fly a combat mission but it's not going to happen unless I can read the kneeboard.

DCS has never been consistent with recognizing switch states. Always assume that a switch in the on position (the throttle in cutoff for example) at the start of the mission is not recognized. It's really easy. Get in the cockpit, move each throttle into the idle and back to cutoff before attempting your start and they will work fine, provided you don't edit any controls before you start the engines, else DCS will again forget about the state of the switches.