MYSE1234

Agreed, that's my experience as well.

This is a collection of texture fixes for the cockpit. They range from minor changes to complete reworks. Fixes for the instrument lighting: More even lighting strength Removing strong banding in the lighting. There's still some, probably due to compression Removed the black paint on panels being illuminated Added "BANA" in "BANA/GRÄNS" to illuminate Added "LJUS RADAR" symbols to illuminate - radar brightness Added "BELYSNING" symbols to illuminate - cockpit illumination Added arrow illumination on FR22 panel Added illumination to "MIL" flag, on the distance indicator Fixed white lines in the radar display moving with the sweep Removed lens flare from lights, bloom is still there Added warning flag on CI to be illuminated Changed FLI needles and wings to be lit more realistically Added dots on panels to see what position the rotary switches are in Nice lighting effect on the altimeter STD "cover" Instruments: Remade FLI37 ball texture to be more true to life and to also show correct pitch angle Added 60° and 90° roll lines on FLI37 Remade the Distance indicator to show the distance more accurately. Range accuracy is now within +- 100m (1000m), average accuracy is +-40m (400m). Clearer and more accurate warning panels. Also dotted a few Å,Ä and Ö, and made some - where they were missing. Clearer AFK light Redder altitude warning light Brighter autopilot and altitude warning lamps Clearer radar range numbers Altimeter "0.5 lines" are larger than default Imperial altimeter and distance indicator (optional) Added text on weapon jettison and X-tank jettison covers X-tank jettison cover is duplicated onto the RENSA cover, but it’s not very visible. Unfortunately can not change this Added emissiveness to α15,5 button Removed mipmap for annunciator panels - better text visibility Pilot model: Subtle changes to the vest roughmet Added missing insignia on left arm. Complete with normal and roughmet Changed velcro textures on right arm Added roughmet to name tag on left arm Reduced the normal detail strength on the gloves Changed color on gloves Slight changes to scarf Sound: New Sidewinder tone VR: Viggen themed main menu This is a custom cockpit livery, after installing it you have to select it in the "Special" settings menu! Modloader ready - installed in main game directory v4.0 Download - passes script IC v4.0 English Download - passes script IC Imperial inst. v4.0 Download - passes script IC - only Swedish cockpit v4.0 - Clear IC Download - passes script and texture IC v4.0 - Clear IC English Download - passes script and texture IC Imperial inst. v4.0 - Clear IC Download - passes script and texture IC - only Swedish cockpit

There is no Fresnel lens in the EP-13, only regular lenses. Most likely what you are seeing is a Moire effect between the scan line effect on the EP-13 image, and the display/pixels on the VR headset. I think it will be difficult getting rid of this problem as we have physics working against us. I agree it's a bit problematic, the scan line effect is much more pronounced in VR than it is on a regular monitor. The scan line size could work as a function of the display/monitor resolution, which might explain why it's more pronounced in VR.

These are all of them, I think: B M BX R L, maybe Basically all you can enter manually on the data panel.

I'm having this problem too. I suspect this might already be reported here:

That uses the F10 map to create a flight plan, but instead of manually placing all the waypoints on there you can let it auto-generate them for you using this. The only input it needs is a mark named "ATTACK", preferably placed on your intended target. It will then automagically set up the waypoints leading up to the target, I think B1-4 with M5 as the target.

Fairly sure I've seen an image of an F-4 with Bk90s mounted on the wings.

No, it's just the roll axis for the stick. You do need some airspeed though for the rudder to become effective (it doesn't effect the nws, only the rudder), so you cant taxi using this "trick", but you can do fine adjustments when taking off with it.

@RagnarDa @Cobra847 Pretty please, I'll get you some (imaginary) cookies. I'll even do the "boring" part for you, as I've already got my spreadsheets setup. I'M READY

Yes, the roll axis and the rudder/yaw is linked, so you are able to steer the aircraft on the ground using the stick in the roll axis.

Would it be possible to tune the bloom effect on the text for the Datapanel and Destination indicator so that it's easier to see that it says. It is particularly hard to read them at night where everything just turns into a bright blob, it's especially bad in VR due to the lower resolution. The Destination indicator is impossible to read at times.

Last update did something to the textures in the cockpit, the lighting has changed quite a bit for the worse. The alpha channels have, for some reason or another, changed and now have some very funky thing going on in them. The effects of that is things such as: The right side panels have the black paint behind the text illuminate - see for example the Datapanel A previous problem is that "BANA" in "BANA GRÄNS" is not illuminated at all. But I guess that is now somewhat fixed Some indicators are now very bright compared to others - see the altimeter,speed indicator, trim, break pressure... Heavy banding on some of them - see the fuel indicator, EPR...

The text size on the Destination indicator is tiny and therefore very hard too see what it says. Especially at night when the bloom effects pretty much hide the symbols completely, unless you zoom in which help some. Compare the current ingame indicator to what the illustration for a manual shows. The number is particularly small, but both should be larger.

I would like to propose making some changes to the RWR we currently have. This is due to my work on the RWR mod, I have spotted a few things I would like to see improved upon. Changes I would like to see: shorter possible signal lengths. Currently the lowest duration for a signal is 0,1 sec, which in most cases not short enough to accurately represent the radar's real dwell time. I found this short clip showing a Viggen getting a radar with a dwell time of 0,015 sec, so that to me should be the highest minimum possible, which is more inline with what would be required from my research. I think having it set to 0,005 would be a good and realistic. Then if the above gets implemented. To not increase the amount of code needed to represent the signal by several times, I would like to propose to change some of the ASCII symbols to represent a longer duration of silence than the standard signal length. So for example, as nothing above 5000Hz will be a single tone, maybe have: "c" be a duration of 0,005*10 = 0,05 sec "d" be a duration of 0,005*50 = 0,25 sec "e" be a duration of 0,005*200 = 1,00 sec It would also be good to be able to set the scan elevation of the radar. Lastly I would like to the the ability to add multiple radars to a single unit, like ships that have way more than 1 onboard.

Trigger safety still up? With it up/ unsafe the display is going to display the selected/hung weapons on the aircraft, which I'm 99% sure is what is going on here. Most likely solution is to safe the trigger/ flip it down. "1" usable weapon on store "Flashing 1" is currently selected weapon "0" pylon empty/ used

Should be sorted now

Max speed for the gear is 600 km/h (320 on the ground), but extend them at 550. The AFK will keep 550km/h when the gear is retracted, and if you were to extend it it will slow down to whatever speed 12°/15,5° AoA is automatically. NWS is always on, there's no way to turn it off.

ED seems to think otherwise..

@cjffly You wouldn't happen to have the axis bound to "T6_Axis: Antenna Elevation? If so switching over to "T6_Axis: Antenna Elevation (Slide)" should fix it.

Thank you! Can't but the same about your Viggen. I do indeed. Unfortunately, but expectedly, some (read "a lot") of data on the radars in-game is classified or very difficult to find. As such, there has been a fair amount of just guessing/guesstimating. The end result of that is that the older cold war stuff is what is most accurate in the mod, as there is a lot more data available on those systems. Here are the sites that I used the most: https://www.radartutorial.eu/ https://www.globalsecurity.org/military/world/links-ground.htm http://www.ausairpower.net/index.html For older MiG's I found this. I do have one update coming soon™ (later today), with an even more realistic version where the radars that are outside the APP27 spectrum (2GHz-25GHz) will be removed for those that want it. The plan is to add new things as the come, like with the NASAMS the other day. I currently do not have anything new planned for the mod, unless the ability to add multiple radars to a unit becomes a possibility. Like with ships that have >1 radar on it, then it would have some work to do. Absolutely not, it would be and honor to have it added.

V3.1 is out with some new and fixed things. Fixed 19J6 - broke with latest patch Added NASAMS search radar Added AIM-54 family A Mk47 C Mk47 C Mk60

Thanks for the fix Cobra! Beware that this breaks IC, so might be problematic if you plan on doing multiplayer stuff.

The aircrafts air intakes are missing in the cockpit view. Wings and canards are still there it's just the intake model that's missing as seen on the image below. Aircraft looks fine when viewed externally.

They're obviously busy making a JAS39 module.

You would think so, but that's not the case.