Goblin

The EP13 displays the view signal from the missile. No missile, no signal, nothing to see in the EP13.

I would also think that you could hear this, if you were aware of it. And the instructor (ex Viggen pilot) at the F15 sim mentioned this sound specifically, which would indicate that it had some importance. I've posted a question at a Viggen facebook group. Hopefully someone responds. But anyway, the sound is definitely there... LNS can't go wrong by implementing it, IMO. After they put it in it's just a question of getting the volume level correct.

A friend that flew the JA says the levers could be split in flight by using some force. It was absolutely not standard procedure but he also indicated that it could give a slight advantage in slow speed dogfights, which wasn't something the Viggen was built for.

In the simulator at F15 the clonk sound is more "hollow". Perhaps a resonance effect of the structure. It is more of a "Tock" than a "Tick". But may I suggest sending a question to SwAFHF and ask if this sound is heard in flight? The Viggen pilot I talked to could not remember hearing it... Could be bad memory, or hearing, or a combination ;) Here's a clip from when I flew the AJS 37 Viggen sim at F15 museum. I'm pulling up in a loop and you can see the ASI winding down past 550km/h and hear the click. It's quite loud.

No more trainers..? Nonsense! Gimme a Tiger Moth to go with the WWII theme! I'm serious!

The sound of the lock is really apparent in the simulator at F15 at least. But I guess windnoise @550kmh and a real RM8 sounds quite a bit more than that simulator did, and a helmet will muffle sounds as well...

My ex Viggen pilot fried got back to me. He could not remember hearing the lock "clunk" when flying, but it did indeed lock the handle. Granted, he spent most his career in JA. Maybe it's different?

Oh, absolutely! I concur. I also use HOTAS buttons and look at switches, and I'm sure voice control would be perfect for many key combos. I just haven't tried that yet. But I was commenting in relation to using hands in VR. Compared to using a mouse or trackball, hand controllers might not be so bad. I think the biggest problem will be where to put them when you need your hands on the HOTAS. It's not a problem finding them, as the depth perception in Vr is excellent, so I just reach for where the controller is in VR. And, ED need to make the hands less obtrusive. Maybe see through, like in Oculus home. Another possible problem with using hand controllers will be if there is something physical, like your HOTAS, situated where you need to move your hand/controller in VR...

This may very well be the case, but should be possible to calibrate. The MC75 is a heavier fuel (higher density=more energy per liter). This could be why you essentially get 7% extra "energy" compared to the older fuel? I don't know. Just speculating. :)

Clouds have a major impact on FPS in 2.0.5. Reported by several. I'm guessing devs are aware and working on it as I write this :)

Like the Wolf mentions, DCS doesn't support cockpit interaction with VR handcontrollers yet. I'm not as eager to dismiss hand controllers though. I use a trackball to interact with the cockpit today, and that means letting go of the HOTAS to use the trackball. It would be more or less the same with hand controllers, but maybe more intuitive... We'll see when the function is fully implemented. Now being able to track you own naked hand, or using thin VR gloves, would be superior. But technology isn't quite there yet. And a possible problem with that is the tracking of individual fingers would have to be very precise in order to track the small movement of flicking a switch, or pressing a button. Here the handcontrollers have an advantage, IMO, since they have buttons.

I remember the "clunk" when decelerating past 550 in the Viggen sim at F15. I can't remember... Did the lock affect the gear handle, or the mechanism behind it? I mean, is it possible to move the handle, but the gear remains in, or is the handle itself locked? I can't remember any sounds accelerating past 550... I have asked a former Viggen pilot I know. Maybe he can help.

I agree with what's been said already. You don't have a deadzone for your head in real life, do you? You don't need one in VR ;)

The airbrakes were notoriously ineffective. Coming out of afterburner made you feel like you had stopped, according to a Viggen pilot I know. ;) And, as mentioned, they weren't used on the JA... So, I think they are close enough in the module.

The radar see objects that's not there, but will be as the mission parameters spawn them? Sounds like this could be a bug within the DCS code..? Anyway, make sure you post a thread about it in the Bugs section of the forum.

:lol: Fantastic!

Good job!

I don't think you are complaining, Coxy_99. And you are of course free to ask anybody anything. But to me it's a bit pointless and unproductive to ask why a bug wasn't found or corrected before a release of a test version. Water is wet. Unfinished software has bugs. ;-) Let's focus on finding the rest of the bugs so they can be fixed. The sooner the better. Cheers!

5. Await green FK light (=targeting gyro speed OK)

I'm obviously not Cobra, but I wanted to voice my thoughts on this anyway. I'm not criticizing you or your post, Coxy_99. Just presenting my view. The Viggen module is still in testing. It's an open test release, not just an early release. And why does any bug go undetected? It's an unfortunate fact that developing software means keeping track of numerous dependencies in the code, that may or may not affect other features. Fixed this, broke that, sort of. I was fortunate enough to test the Viggen before the 27th of January, and I don't remember it being that unstable in yaw. Sure, a little bit perhaps, but not like the build that was released on the 27th. So, maybe something changed in the code for 1.5.6 (which is also a test release), or something in the module build, that made this bug more pronounced so that it was discovered. I immediately reacted to this problem once I tried to take off in the open release build :) This is the nature of testing software... If someone wants a finished product, wait until it's finished.

I have asked around and it is the caution lights. The Viggen pilot I asked couldn't quite remember but he said that caution light checks normally included pressing the caution light panel test button. He thinks ITF is short for "Indikeringstablå Funktion". That translates to "Indication Panel Function (or test). and means the panels with the caution and warning lights, which also contains normal indications such as landinggear and speedbrake, hence the name "indication panel" and not Caution/warning panel. Ground crew aborts turnaround ASAP (as soon as possible). Delay 30 - 90 s Emergency takeoff may be performed without flight control stabilizer in case of apparent danger. (GSA=Grundstyrsystem. I.e. The un-stabilized flight controls before SPAK/ATT/HÖJD is engaged) 'As required' sounds better, and is commonly used in english language checklists.

That's reported and devs are aware.

^What this man says that man said!

Yeah, I'd say the ground rolling yaw instability is fixed now... Will of course test it some more. I have a regular 15% curve on the rudder axis. i normally set a curve of 10-20 on all axes. Positive yaw control without overcorrecting or entering PIO.

Tested post patch and now it's perfect! Good job, RagnarDa!