MYSE1234

If this is what you want... Yes. Right here, AJ37 SFI del 3, page 83-97: https://drive.google.com/file/d/0B8bCDRcq9BVeY0gycWRrMXVIdTA/view

Black is the returns, white is just nothingness as far as the radar knows. Black = something hard.

The chair is too high to see the HUD symbols, which is why you see it when you lower your head, and those are not fragments that's pretty much it. Lower the seat and you should be good.

Yes that should work. If you're using the ME I would probably input ToT manually be extra sure for it to work correctly. I highly recommend using CombatFlite for doing cartridges for our Viggen, it's super easy to set up waypoints with ToT and all kinds of WPs (Ruta, Bx1-9). The CK37 will however not continue to calculate time error after the last target WP that has a ToT set, not sure if that's currently a thing in DCS or not.

To see time to take off you need to have a K-time (ToT) set for your target(s). All you have to do to see time to take off is setting the knob to TID and UT. That should give you a some thing like: ☐01254. 12min 54sec to take off. Make sure to have LS selected when doing so. The runway thing is probably just that the CK37 has a default runway that it uses, but that the pilot can change if needed because of the wind or whatever it might be. The computer should also do that automatically anyway so not really needed.

Makes the engine create more thrust at low speeds, it also makes the reverser work. At high speeds however it does the opposite, it will decrease the thrust created. Which is why it's closes when: M>0.65 Landing gear is up Throttle at or infront of Z2 ignition position - ≥Z2 Inlet seal in open It will open back up when one or more of the above requirements are NOT met. Here's all info you want. More or less.

No fun has been ruined. I love me some new C O N T E N T, even if it brings some bugs with it.

That's a known issue, should be added in a hitfix on friday if there is one.

Same for me too, forgot that one.

Love all the things added, thank you RagnarDa, and the rest of HB. These are the things I've found so far: Game crash when shooting the last sidewinder, no matter how many you bring. The last one WILL ruin you. IRRB Framstegning still not working, there are more keybinds however RB74 super smokey, while RB24J is smokeless Can't really see any difference with or without the radar night filter Oxygen hose on the pilot model missing it's texture

In the GR video you're refering to Cap is using the A-A mode for AKAN, AKAN JAKT. When using that mode you will get a radar picture. The mode you are using however, A-G, will not get a radar picture as the radar is used for radar ranging instead. Try using AKAN JAKT and see if it works better.

Adding a curve to the breaks helped reducing instability when breaking for me.

Thought I would give this thread a bump.

Well yeah, of course. Just didn't feel the need to write a 5 page essay about it. :smilewink:

HÖJD uses the static pressure from the pitot tube (Ps). When you click the the button to engage HÖJD, the static pressure gets saved as "Ps-ref". That is then gets continuously compared to Ps to get a height difference. If there is a difference, the resulting error signal get directly sent to the outer rudder servos, to get the aircraft back to the the correct altitude.

From what I've understood from the manual, the current behaviour is the correct one. The altimeter has nothing to do with the reference height/ pressure used in "Höjd".

About 13 000m, with a clean jet.

Definitely something different. :pilotfly: Reached 2.05 before running out of fuel.

It works fine for me, using the open beta. What did you do to change it to a target point? Just to rule out incorrect procedures. Should be TAKT, 9 and then select the WP.

Here's what THE manual says about the topic:

Lin while using ground avoidance mode is what's recomended in the manual.

I wouldn't trust that book too much. The latest swedish jet that could carry bombs that big was the A32 Lansen, serviced 1956-'78. Except for Gripen of course.

I think he might be thinking about this. https://en.wikipedia.org/wiki/FFVS_J_22 Then there's this monster. https://en.wikipedia.org/wiki/Saab_21R

I got the same message, when using the exact same setup. But for me it happened on takeoff.

I'm pretty sure you have to change the dial to select the airfield that you want to speak to. You might have some problem comunicating if you're on the wrong frequency. :smilewink: In sweden the air force wings are designated by a number, for example F21. In the Viggen that number is used for inputting the takeoff/landing location(LS/L1/L2), "9021" or "9921", aswell as the number used in the base selector on the radiopanel. The name for the dial is "Basväljare", base selector. As in airbase selector. So if you take of from lets say F7, for take off you want the dial to be on 7, so that you can speak to the ATC at your take off base. Then when you are approaching your landing base in this case F21, you change your dial to 21 instead of 7. That way you will have the correct freq right away, instead of messing around with the manual selectors. The letters are different frequencies for the base that you have selected. D is a regional channel, whatever that means. The numbers in DCS have the same function, but are not based on the "names" of the air base, but rather just randomly given by the programmers that made our lovely Viggen.