Jump to content

Recommended Posts

Posted

x6 tries now, following a single successful F-18 sortie in MP. Did one more in SP and the same thing happened.

 

Viggen starts fine. Usually about the time I'm about to roll out of the hangar, CTD. No crash dialogue. I was trying to use F10 map marks for Nav and thought that might be the problem. So, I did a couple of tries by manually inputting Nav information. No change. Also, each and every time, I had loaded BK-90's. Didn't attempt anything else.

Logs.rar

  • 3 weeks later...
Posted

Nice job: the latest update removed this annoying thing, but in several missions the left main gear is still out after retracting gear (by command). It does not seem to influence flight behaviour, but it is there :notify: control panel does not care for it.

Screen_190426_194541.thumb.png.8e8ec178a06845a5fdd50972f5f3671d.png

Screen_190426_194549.thumb.png.59b769dd03f32e600c92d2c1a62ebd20.png

Posted
I had that bug with the gear once as well. No idea how to reproduce it.

 

+1

Visit https://www.viggen.training
...Viggen... what more can you ask for?

my computer:
AMD Ryzen 5600G 4.4 GHz | NVIDIA RTX 3080 10GB | 32 GB 3.2 GHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TRP | Rift CV1

 

Posted

Was it after hard landing/over speeding while taxiing? If so this is the simulation of damaged gears. This happens in DCS side and I don’t know of any callback in the SDK for this hence the confused indication lights.

DCS AJS37 HACKERMAN

 

There will always be bugs. If everything is a priority nothing is.

Posted

For me it was during a normal rotation. Might have hit some FOD on the runway, not sure. But again, the gear had no aerodynamic effect on flight. My wingman could also not see it on his side.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...