MYSE1234

Here is a list of all the airfield currently on all the maps, together with their respective reference number. This is the work of @Wali, who said I could post it for him on here. Thank you for taking the time to get it all compiled into this nice list. For the rest of you, I hope you find it useful. Enjoy!

"9043" But not sure it actually does anything, haven't tried it. Works fine for me.

They're not working in that the brakes won't actually break the aircraft when manually setting the parking brake. They work fine when you first spawn in, but after that they are non-functional. The animation works fine, It's just the braking bit that could do with some fixing.

Version 3.2 Removed all radars outside the RWR working range! Download link on first post. 55G6 Silenced PPRU-1M Sborka Silenced P19 Silenced NASAMS - “AN/MPQ-64F1” PRF to 1600Hz Dwell time to 0,1sec Rapiere LN Ambulance tone for search HQ-7 Search PRF to 3600 SA-2 “Fan Song” Lock PRF from 2500Hz, to 2900Hz SA-11 “Fire dome” Scan time to 20sec Added scan area 120° (+-60°) Carrier freq to X-band - 8GHz Search PRF to 2400Hz SA-11 “Snow Drift” PRF to 800Hz, from ambulance tone SA-6 “Straight Flush” Lock PRF to 2000, same as search. Was ambulance tone SA-15 Search PRF to 4800, was 2000 SA-13 Silenced 64N6E “Big Bird” Search PRF to 200 Carrier freq to 2,9GHz 30N6E “Flap Lid” Lock PRF to 500 Roland Lock PRF to 5000

I tried it, but the material on the that model is not set up to be self-illuminating unfortunately. So we'll have to wait for HB to get that fixed. The texture file for it is in the pack, so all they have to do really is to change the material to self-illuminating.

That's what I was thinking too, but from my testing I see nothing pointing to that in DCS, it might be the case irl.

Why not both? I know for a fact that the release cue is not shown at the (assumed correct) distance shown in a diagram in one of the manuals, but only at high speeds. We've got two diagrams showing the release envelope at: "100m and mach 0.9", the max range shown there is 7km, directly in front "100m and mach 0.7", there the max range in front is 3,2km, +-50 or so The cue I got when testing this some time ago at "100m and mach 0.9" was at 5,1km, so about 73% of what it should be, according to the manual. The slower mach 0.7 is very accurate to what is shown in the manual, with a distance of 3,16km. Well within the margin of error. To have the cue at the correct mach 0.9 distance is impossible, from my testing. NOTE: I only tested up to 550m, so it might be possible to get the 0.9 cue accurate at higher up, but from 450-550m it's a constant distance of 6,6km. Image below is probably ONLY, accurate in distance directly in front of the aircraft. I did not test drops to the side, as that should have take too much time to do.

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..