Kiwispirits

Any update on this please? I have given up on the JF17 for CAS and switched to the Harrier because of the poor targeting pod picture in the JF 17

Alt-enter no longer maximises the VR mirror. Pain for VR, because despite selecting "mouse confined to game window" I can still unfocus the VR mirror and headset by clicking in my periphery while wearing the VR rig. Been that way for years, through 3 different rigs on different drivers and platforms. Alt-entering the mirror was the only way of fixing it.

Thanks Foogle

While the radar is in Intc TWS mode, S2_right does not change radar azimuth. The button beside the display does change the azimuth. While in RWS mode, S2_right DOES change radar azimuth, and so does the button beside the display.

Thanks for the update uboats

Is the targeting pod working as expected in CCD mode please? It seems to lack contrast regardless of level controls, which makes it hard to pick out objects in crowded areas such as trees/towns. Contrast is low compared to the ATFLIR pod on the FA 18, although I appreciate that is a different pod on a different MFD type. The JF 17 IR mode has much higher contrast but of course has disadvantages for cold objects.

Unexpected, but confirmed

You used to be able to turn off all the buttons on the AAP panel by holding the OFF button down for a few seconds. This no longer works. You can turn all the individual buttons off one by one, except the AAP INS button.

Thankyou:)

The JF-17 Tacan has 10 presets, all preloaded with airfield Tacan data. I know I can select these presets and over-write them with Tacan data from briefings etc, but I would like to know which airports the original preset data represents. I cannot find any chart or form describing which airfield corresponds to which of the 10 Tacan presets. I found the chart in the kneeboard that describes airfield numbers for navigation uses (airfield 50 etc) but there is no data on associated Tacan preset numbers. Does anyone have any ideas on this please?

The new lighting looks wonderful at night, brightness knobs work just right. However the lighting is too dim to be seen during the day. I like cockpit lighting in the day as it makes the instruments and controls more readable when they move into a shadow, especially as I use VR. I can see what you were trying to achieve, but it is almost like you need a day/night switch for the cockpit lighting.

Has Deka indicated if they are going to create more missions for the JF-17? I know they are working on bug fixes but the lack of current content must be hurting their sales compared to other early access modules.

If you get really annoyed at the guy in the jeep failing you for missing a switch or something, you can use the gun to blow the jeep to bits. Just rearm and load gun ammo, arm master and gun switches and arm the ground test switch way over on the left rear of the cockpit. You have to nudge the Hog slightly to the left to hit the jeep.

Just to say this bug is still in existence

Just adding my voice to those who crash on the last mission of Mjolnir. Did it successfully twice, crashed DCS on exiting mission both times.

I think you might need to sticky this thread. You want people to read it before posting in bugs, but this thread has slipped to page 3 before I made this post.

happening here as well (Hastings New Zealand)

I am considering purchasing this module but I am one of those strange people that enjoys the study aspect and in particular good training missions. How many training missions does the module come with at the moment please? I realise that it is in early access and as such training might be limited until they fix the most common bugs, but I live in hope :)

Just recently started playing campaigns for the Viggen. I use an HTC Vive VR headset, GTX1080 video card, 16gb ram, CPU i7-6700HQ @ 2.3GHz. PD1.2, all other graphics settings at minimum except textures at high to allow reading of labels in the cockpit. The Mjolnir response campaign works fine, no appreciable stuttering. The 1st mission of the Red flag mission is totally unplayable, just a stuttering mess, freezing every second or two. Looking out the cockpit the game appears to be very slow in rendering the NTTR landscape. Is the difference just because of some hidden property of NTTR versus Caucasus? Perhaps the four AI viggens in front of me for the Red Flag? Has anyone else had this problem, and any idea how to fix it please?

I recently saw a youtube video from Grim Reapers on how to adjust your view position in the cockpit ( ) . The commands they used (cockpit view?) work in both VR and non VR. Moving the cockpit view to the top position in VR (similar to raising the seat height in the real aircraft?) for takeoff and landings makes things much, much easier as there is more runway visible i.e. less obstruction by the engine cowling. All sounds simple in retrospect, but I never thought of it even after flying for 18 months.

.

I suspect there is more going on in the control bindings files than DCS are letting on. I recently had problems with orange duplicate lines in my Viggen and today they have appeared in my Harrier setup. They do not go away with repair, and I am not using any external tools or mods. Something is slowly corrupting these files. Filed a ticket about it and got told they do not fix things developed by third parties. Wonderful.

.

.

.