CaptCrash

found it

I recently got back into the viggen and the pitch issue on take off is frustrating. I remember someone posted there was a landing gear suspension mod (non-ic) that was available. Does anyone happen to remember it or have a link to it? Thanks!

Thank you!

What do I do with the elint xml file? Thanks!

I'm sure @IronMike will appreciate the info. Nice work @rossmum

Is there a current complete change log for the viggen?

This is a known issue and is on the heatblur roadmap

I have all the NATOPS for the OV-10A/D and aviation experience as well as experience in generating polars for airfoils, would be glad to help out to make an OV-10A/D. I am in the beta for the HotStart CL650 and the 747-200 for X-plane.

My post from a while ago just had a slight pitch change maybe 5 degrees either side of vertical and that is what did it

might be worth tagging mike on this

sounds like this issue here:

My guess is that the attitude indicator is what is causing the nan since DCS would be using quaternions for the flight model

Doh, I did search to see if i was reporting something old but didnt come up with anything.

During a constant g load when passing the vertical the g meter will either add or subtract one g. This is incorrect because the vector addition of g from earth's gravitational field should follow the sin of the pitch angle not add or subtract g depending on passing the vertical. The vector of g is [sin pitch, cos pitch]. Just to be clear I am not referring to the induced g load on aircraft which is of course contingent on the radius of the turn and the velocity of the aircraft, but specifically the gauge should not instantly drop 1g upon passing the vertical effect of the gravitational field on the g meter

Confirmed as well after 3 half cuban eights, the fourth crashed. edit: I was able to duplicate by flying level ->pull up slightly past vertical -> push forward to slightly past vertical. So level -> ~+95 degrees pitch change -> -6 degrees pitch change and the sim crashed. I am also in the latest open beta edit 2: checked the log: 2021-10-29 05:20:26.653 ERROR VIGGEN: HeatBlur: Assert failed: Value out of range. -. Was nan. Expected between 0.000000 and 6.283185 @ e:\dcs\viggen git\ajs_5\trunk\viggennew\sources\flightmodel\flightdataunit.cpp:695 Tacview-20211028-221902-DCS-04 - AJS37 Training Basic Navigation.txt.acmidcs.log

Thanks!

Why does V3 fail IC? I'm not well versed in the IC requirements so apologies if this question has a very obvious answer

Remarked as DCS issue

Fair enough, Looks like an Eagle Dynamics bug then....

I didn't see any difference between leaving the knob at 0 and setting it to +6 at Caucus. Is it functional?

If the HUD is inline with the exhaust effect of a jet aircraft the HUD becomes blurry. It seems like the HUD is drawn to screen before the exhaust effects causing the hud to be affected by the exhaust effects. DCS Issue

Ya it makes precision navigation very difficult especially when you need a precise line up for a target. Hopefully @IronMike can add this to the list to get resolved. 5 degrees/hour for this type of system would exceed the 2-sigma 1 degree/hr probability of heading drift. I was flying the second campaign where you do CAP in the second mission and the HUD/FLI37 disagreed by about 7 degrees by the time i was called off station, that would cause a gross navigational error and warrant replacement of the unit - if it happened irl. Edit: To be clear this also affects the Central Indicator ring.

would this affect the HUD waypoint direction? I noticed if i stick the flight path vector on the indicator course it's pretty inaccurate but if i offset about one vertical line im more accurate. edit: the compass rose after some time will disagree with the HUD as well. I'll try and get a photo later tonight. edit II: Here are some numbers I computed based on the video Delta Time: 1.20694hrs (Start: 08:00:00 -> End: 09:12:25) Approx Drift: 6 degrees Drift Rate: 4.971 degrees per hour which is ~5deg/hr or 0.083deg/min. so still about 5x higher than stated of 1 degree/hr @MYSE1234 can you confirm the time stamps in the video are HH:MM:SS format?