mdee

Corvinus - thanks for looking into this. #1 I may be getting something wrong but IMO any value should work. B2 is M2 and works like reverse bullseye and U2 is a bullseye - so distance/heading to M2 should work no matter how far/close the waypoints are. IMO. I recall I've tried different distances (~7km) and going straight to U2 from B0 and switch still didn't happen. The switching sequence - B0 (start), B1 -> U2 -> M2. In my Nevada mission I am guided correctly for about 10 km to U2. But then circling begins with no switch. #2 yeah, observed that too Overall it feels very unpredictable. I'd not use it in combat ;)

Confirmed, also I have trouble with A0/A1/A2 modes. The sight is always white on black.

Same deal on Caucasus. 3491 popup (also tried 349100). viggen_test__caucas.miz

Thanks for trying, much appreciated. Nice! The programming was really bad quality, they don't make shows like in 90's anymore ;) I'll try Caucasus,

Mission attached. viggen_test.miz

Yeah, you right, "normal" = "switch". I set up mine so up is one logical button, down is another.

Not sure - I never changed it, left it how it was by default. I doubt the throttles have different PCB versions, but who knows - if you really want to know, Cyp3r is your best bet.

Shouldn't be necessary, but yes I did try 330100 with the same result.

Yeah I use it, but considering what Virpil software already can do, I guess they could add chain and tempo too, so I'll have to use gremlin only for very special cases.

The profile I've attached does exactly what you want.

Ran into this issue, wanted to confirm if it's me or a bug. Flight plan: B1-B2, in NAV mode. TAKT - IN - 9 - B2 (B2 --> M2) 3301 - B2 (created pop up point U2 10 km from the target approaching from south towards north) OUT - AKT/POS Flying towards B1 > U2 (as expected) then nothing.. stays at U2. M2 never selected unless B2 pressed manually. ANy ideas?

Agreed. My suggestion for mk II, after using Mk I for a month+ Remove big red/yellow button, add 2x3-way toggles in place of it I'd rather have additional 2 square buttons in place of covered one Analog stick instead of 5 way hat would be nice to have, but not essential Tempo and chain functions in software Very utilitarian and won't look so "cool", I know. Overall rather minor tweaks and I bet everyone has different opinions.

Logical vs physical buttons. Physical button 28 is mapped to logical button 32, so is 29. You need to remap physical button 29 to next available logical button and change function of both (28 and 29) to "switch". Check the profile I've attached in this post. Ignore joystick gremlin part. https://forums.eagle.ru/showpost.php?p=3646635&postcount=31

Thanks for this, it's brilliant. Would be happy to pay for this. I'll pay if someone does the Viggen (computer) :)

I really disliked the knurl on the pictures, but in person it's pretty good actually. Grew on me :)

Thank you!

Frederf - thank you so much for this information! And, yes, INS updates issues - offset effect you described - spot on, noticed that too. I've switched over to offset coords instead of polars and have much better rate of success now. I hope little quirks/bugs the system has now are going to be fixed. It's a very fun thing to do, especially when simulating low visibility conditions.

INS position update (as described in the manual - no VAL press) after selecting P1 (does not work) or cursor position on the HUD is not updated properly. BAD doesn't light up after INS position update Bombs elease immediately after trigger is pressed.

Still broken here. Current beta,

Listed above bugs are still present. Not missio bugs tho, these are module bugs.

Yeah.. after 50+ runs I am coming to the same conclusion. A couple of things I've found - VAL pressed like normal update works much better - Toss the bombs (30 pull about 15 km to target) - Have a big target and long interval :) - Use a JTAC

Had a slightly better success if I pressed "VAL" as per normal INS update, but only slightly. Also, pressing pickle releases the bombs immediately....

Hey Thought I'd ask for help here as I can't get INS bombing right - always off 10-20 meters and I am not sure what causes it. Here is what I do 1. Aircraft ready to go on a runaway, started up. 2. Check theta/rho offset from designated IP waypoint. I've tried both to measure it on F10 map and in mission editor. The differences are minor. 3. Target is about 12 miles north from IP point. 4. Alt difference same as in #2 (waypoint alt - target alt) 5. Stick the data into INS as BAD waypoint in reference to IP waypoint. I am positive I am entering the data correctly 6. Set weapon release parameters etc. Take off. 8. About 3 miles to IP waypoint, Master Arm on, P1 selected (RS etc. is on too, the aircraft is configured correctly), INS update diamond visible on the HUD. "X" waypoint visible as well 9. Point the diamond at the landmark, press "target designate" button on hotas tu update INS. THe "X" on the HUD doesn't move. "VAL" lights up (I am not pressing it - going by training mission), "REC" lights up, but not "BAD" (according to training mission it should?). 10. After overflying IP I get CCRP wings guiding me to the target. 11. "X" on the HUD is usually about 20-30+ meters off and not lined up with the target 12. The bombs miss, consistently. I am bit puzzled. This is supposed to be a precise method. My theory is that measurements in the editor aren't precise enough - if this is the case how can I measure the offset better? Any other ideas?

You can do button to axis assignment on mini stick and use curves etc. to make it behave really smoothly. No issues whatsoever. Analog stick would be great, but it's not necessary.

Did you reload the profile? Manual is here https://forums.eagle.ru/showthread.php?t=219597