Kiwispirits

Really enjoying the training missions thanks Baltic, especially the Easter egg at the end of the cold startup :) . Is there any chance of having the start-up kneeboard checklist (and any other relevant checklists) as a separate file please? That way I can add them to my own Harrier kneeboard and pretend I know what all of it means :) Edit: Do not worry about this please, I found that if I use 7-zip to peel the mission file apart then the kneeboard page images are sitting there ready to go in their own folder. You really do a lot of work for these missions Baltic.

Thanks Holton. Nice to know the cause, but slightly depressing that stuff like this is left unfixed.

I have been struggling with orange duplicated lines in my Viggen control mappings for a couple of days. I have tried all the advice I can find on the forums for similar problems (checking lua files under saved games etc) but nothing worked. So I uninstalled DCS completely and removed the user\save games\DCS.openbeta folder, and any left over bits from the main installation in the Eagle Dynamics folder. I downloaded DCS openbeta, ran it and downloaded the AJS37 module. Absolutely nothing else. And I still have the duplicated lines, screenshot attached. Perhaps I should just take up knitting?

Tried uninstalling and reinstalling the Viggen, still have the duplicated lines and no way of removing them

I have this problem as well. It appeared after installing F-14, then mapping some controls and axes for the F-14. My viggen mapping now has lots of duplicated red lines in it.

Thanks for all your help everyone. Really enjoying your training missions Corvinus.

On a number of threads I see people describing the use of the reference button for a final alignment of the Viggen Nav system while aligned on the starting runway. This has confused me (an easy thing to accomplish) as I though (from the plane manual) the reference button only reset the Nav reference altitude , and that the Nav position fix was manually updated using the Tv button while the radar is off. What have I missed please?

I am doing some of the Viggen training missions from cor.vinus (https://www.digitalcombatsimulator.com/en/files/3302241/) and in one of them the mission briefing requires you to build a landing waypoint for a short runway via Ref/lola and an airport code, and then the runway heading via bana/grans. I am happy with the mechanics of doing all this, but I wondered what benefit the runway heading data gives me for landing? This is not a TILS landing.

Thanks for the advice Rudel, that was exactly what I needed to do to contact ATC and get the runways lit up. :)

On the night landing mission I cannot get the airfield to turn on the runway lights. I tried communicating with the ATC, but the options under ATC in the comms menu all are greyed out and ineffective. Am I doing something wrong please? Otherwise I am enjoying the missions you have so kindly created.

On my Viggen control mapping screen the HOTAS square is greyed out against the Eject command. Keyboard works ok, but clicking on the HOTAS square to map it does nothing. Do others have this problem please?

Found the cause of my problem. I was using some downloaded checklist files, and the folder embedded in the rar file was named ASJ37 instead of AJS37.

Found a small bug with trimming the rudder. The rudder trims left and right ok using the keyboard.When I bind some controls on my HOTAS, the trim right works but the trim left does not. Same control works ok on other aircraft so it is not a driver/config/hardware fault. HOTAS is a Saitek X52. Does anyone else have this? Not a game breaker, but slightly irritating when in VR as keyboard is harder to use.

I cannot get custom kneeboard pages working in the Viggen. Even using images from other aircraft such as the Spitfire will not work in the Viggen but still work ok in the original aircraft. Directory labelling and structure is identical for the kneeboard pages and the kneeboard directory is named AJS37. Does anyone else have this problem please? Very annoying for me, as I play in VR. Having to take the headset off and on 20 times during a startup process to check the list really ruins the immersion.

I was doing free flights over Normandy. However, it was while doing dogfights over Normandy that I blew engines in the past. Will do some more testing tomorrow.

It has been a number of months since I flew the Spitfire in earnest, so I was surprised last night when on a free flight that I could not overheat the engine. I had the Spitfire hanging on it's prop at about 30 deg, 90 mph on full boost and full rpm. I did this time after time, and although the water temperature came up it did not reach maximum and the motor refused to blow smoke and die. I also flew the plane around in more normal attitudes at max rpm and boost and still no motor damage. I had a look through all the settings and it is still definitely on simulation rather than game mode and I cannot see anything new related to hard-to-destroy engine settings. I find this behaviour strange as in the past when practicing dogfighting using the quick mission menu my engine would blow if I fought in the vertical for more that 15 to 30 seconds. Am I imagining it, or have others noticed the same thing please?

Armored glass green tint obscures runway completely Has anyone else had problems with the DCS spitfire on the Normandy map having problems picking out the actual runway while in VR? The green tint of the armoured glass is just the right shade to cancel out the runway when looking through it in VR while landing. The landing strip and the surrounding airfield are just a flat plain all the same colour. It all works ok looking out the canopy, it is just the green of the armoured front plate glass that causes the problem for me. This problem has been there for a month or three, was hoping an update would fix it.

Nothing wrong in my logic. As a new customer, all I see is what I pay for and what I get. I paid for the Harrier, knew it would take a while but I did not expect this length of time. Certainly the F18 has more resources behind it but customers buying in the DCS shop do not know that. I paid the same amount of money for both modules, one is being finished quite quickly and has lots of update information and the other does not. There is also a world of difference between whining and complaining. I offered a solution to making customers happier: publish what you are going to fix and when, and stick to it. This would cost nothing. My post DOES have the chance to change the situation, particularly if lots of others feel the same way and also post: that is the nature of free speech and the internet. If I say nothing, then things will definitely NOT change.

I also feel the pace of fixes in the Harrier is too slow. I have owned it for a while now, and it is noticeable how much faster the updates to the F18 are happening and how much better they are being communicated. Razbam have failed to publish their update plan for this module. I am sure many more of us would be more tolerant if they gave us some certainty about what is being fixed and when.

The only way I would buy this module is if they finished the AV8 first.

I agree with the original poster - although my conversion from 1.5beta was running ok, it runs smoother and with higher settings when I did a complete reinstall from scratch. Worth while putting up with all the downloads.

I am guessing that a lot of VR users already know this, but I have not seen a posting on it: In VR you can bind a HOTAS button for the communications menu, but the standard cockpit selection green/blue cross pointer for the mouse is unable to interact with that comms menu when it displays. However if you double click the middle wheel of the mouse the cursor changes to a white arrow which allows you to click on the comms menu. Double clicking the mouse middle wheel brings back the normal cockpit selection cursor

I have found in the past that higher-powered devices plugged into USB slots can cause crashes. Given that it does not crash when using a powered usb you most likely have a hardware issue with the power supply not being strong enough or too much resistance in the wires leading from the motherboard to the usb slot. Just stick with the powered hub.

I have been plagued with a crash problem using my Vive VR in DCS 2.1/2.2 If I ran Spitfire in Normandy on the Low graphics preset, all ran ok. As soon as I increased the graphics markedly by turning on Deferred Shading or increasing Textures to High, the game would crash during the loading of the spitfire module, throwing up Out of Memory errors and/or DCS.exe has stopped working. I finally managed to fix it: 1. I went into the Steam VR interface and turned off 'Allow asynchronous reprojection' . Reran the game, and of course it was blurry, stuttering and horrible BUT it did not crash. Not even when I set the graphics preset to High. 2. I went back into the Steam VR interface and turned ON 'Allow asynchronous reprojection' (AR). The game ran fine without crashing even on the High preset. I suppose there is some logic in the fix in that AR is the mechanism that is designed to smooth out missing frames, and the number of missing frames will increase as the graphics detail is increased. I have no idea though why turning AR off and then turning it back on should have cleared the background problem that was causing the crash. Hopefully my experience will help anyone that gets the same problem

I managed to fix this problem, but I do not know exactly why it worked. I deselected 'allow asynchronous reprojection' in the Steam VR interface, and ran the game using the Medium system preset. The game ran, but with blurring and juddering (i.e. missed frames). Turned the asynchronous reprojection back on (still in Medium) and the module ran without crashing. Even runs on High now. It would seem that something was going wrong with how Steam VR was handling missed frames - which is what asynchronous reprojection (AS) fixes, but I do not know why toggling (AS) got it working properly.