TOViper

OB 2.8.2.35759 SP Caucasus The mission shows the info screen for B1 at the top right corner. When the audio starts, the ATT and HÖJD buttons are hightlighted immediately, making a pilot look at them while the audio is talking about the destination indicator, which is very confusing (dicactic nonsense). The highlights should be shown a little later, when the speaker is talking about the autopilot.

If you use HD bombs, fly not higher than 150m, fly not slower than M0.8 and lower the hud. Make sure QFE is set correctly in order to see the mark on target for correct timing.

Currently I am finding no other words than ... pffff. How can the year start great without seeing what one wants to see? Hard to believe the Viggen has no fixes, but that's how it is. Next milestone: Wait for ED's multicore in order to increase frame rate ... at least.

"Is the development actually dead?" If one looks at the current changelog, one could assume that, yes. I hope they just forgot about to post the changelog...

Yep, it seems there is no way around MIST function: mist.getHeading(unit, rawHeading)

Hey Rudel! Thanks for answering, but how can I then use this parameter? Only in a trigger condition like "COCKPIT PARAM IS EQUAL TO ANOTHER"? What I in fact need is the current magnetic heading as number ... nothing more and nothing less. Sounds easy, but currently I didn't find any solution for this easy task.

OB 2.8.1.34.667.2 SP (Mission Editor) AJS-37 When I try to save the current magnetic heading ("BASE_SENSOR_MAG_HEADING") via the trigger action "X: COCKPIT PARAM SAVE AS" to a global variable called "heading_start", the value seems not to be saved. See mission file: Tester.miz

Thanks for the hint with the command list. What I want is in fact working in this way: null

600m AGL

No, I want to trigger it with a trigger.

Hi folks! How can I trigger the "trim hat" for activation of the autopilot standard turn left/right? I can see that a depress is an internal function of DCS labelled "iCommandPlaneTrimLeft" and "iCommandPlaneTrimRight". But how can I trigger it? "Cockpit argument in range"? Where can I find the argument (number)? The ...\Mods\aircraft\AJS37\Input\keyboard\default.lua doesn't show me the argument... Thanks for any hint! TOViper

Mode NAV It seams only happening when really firing a weapon; I used trigger unsafe without firing the gunpod, and no fix is beeing made (according to manual). If I really fire the gun, then a fix is made and the waypoint M2 is then at the location of M1. I trigged UNSAFE far before overflying the waypoint. See TRK. It seems that the fix is - in fact internally - done after the switch to the next M-point is initiated by the CK. AJS-37_Training_Nevada_Rb75+AKAN_target_fix_problem.trk

When firing pods in NAV, a target fix for the M-point should be made (this is before overflying the waypoint). After overflying it, the system should switch to the next B-point. When firing pods in ANF, a target fix for the M-point should be made (this is before overflying the waypoint). After overflying it, the system should stay at that M-point. What should be checked with the current OB right now is the following: When NAV is selected and the exact moment has come for the navigation system to switch to the next waypoint, trigger SAFE should be already selected by the pilot. This should in no case change the coordinates of the next M-point. If it changes, there is something wrong.

OB 2.8.1. SP Caucasus I want to release chaffs automatically by using the KB mode selector position "A". I get shot at by an SA-6 missile, and then initiating INT or KONT doesn't do anything on the dispenser pod. I am not using the U22 ECM pod, only dispenser pod, see track: 2023-01-12_AJS37_KB_mode_selector_A_doesnt_work.trk

If this beautiful beast was a woman ... Man, that skin got something!

Yeah, absolutely! I followed the old rule: Don't touch a control unless you really know what it is doing with your aircraft ... so: I KEPT MY DIRTY FINGERS OFF

Hello Machalot! Thanks for this information, but the manual is now in hands of Heatblur and for the moment away from my desk. I will not do any further changes to RC2.1(beta), unless Heatblur wants me to do so. Now I wil start taking care about my new project, which should become live soon. Kind regards and best wishes to you on this NEW YEARS DAY: https://www.youtube.com/watch?v=Wqvry4fM0zk&ab_channel=TonyRomanov

No. The original is pixelated too.

DONE Guys, the RC2.1 office closes now, and re-opens on Sunday for a very short time, when the final version will be prepared for Heatblur. From now on I will not monitor this thread anymore. Thank you for your valuable comments! I wish you all the best for next year, and keep up the good work and mood!

I am currently working on the problem with the implementation of the used font into the PDF the document. When viewing in the browser, the font MinionPro is replaced by a standard font, which shouldn't be. Anyway, this should solve once I use my other compter with the official Adobe PDF printer.

Curious as I was after reading Myse1234's post ... Never used this knob because it was listed in the manual but with [no function]. Funny story this is LOL

DONE DONE No need to worry, they are numbered using the label picture functions of Word, and therefore will always automatically update when new pics are added. Same for references, they are automated fields. Nothing to do here. Can you provide a list? I case yes, please provide only names of testers who want to find their names in the doc.

No, they are obviously not doing the same, since the picture changes when going through the different stages. But it is hard to describe what they really do in the background by just looking at the radar image only. I guess the coder of this certain function should know what the different stages do ...

I tested this with the Moskva ship, and put my radar against it. The ship starts to jam, but with the filter I was able to get the strongest radar returns at the location (bearing AND distance) I placed the ship on the map, ... so: AS JAMMING WORKS! To give this section just a little text, I would add something like this (basically). Radar controls AS-mode selector: Toggles anti-jamming filters. With the filters, it might be possible to determine the distance to a jamming target, and then e.g. perform a successful target fix.

Would it be worth to be included in the RC2.1 manual? Two days are still left ...