TOViper

@IronMike Please note, this keybinding is still not working in latest OB 2.8.8.43704. While the sound for depressing a button is played when using the keyboard binding, the button in the cockpit is not definitively not depressed, thus no test is carried out. Problem here is obviously that in the file "clickabledata.lua" the line 475 elements["warnpanelcheck-PTR"] = default_button(_("Warning Panel Light Test"), devices.ERRORPANEL, 3002, 344) shows 3002, and in the file "default.lua" the line 258 {down = 3001, value_down = 1.0, up = 3001, value_up = 0.0, cockpit_device_id = devices.ERRORPANEL, name = _('KONTROLL light test'), category = _('Lights')}, shows 3001 for depressed state. Also, this keybinding has a wrong name in the file input > keyboard > default.lua (and maybe in a few input files more) It should be labelled with "KONTR LAMPTABLA Indicator and Warning Table Test".

I can clearly see in the video what you are talking about. I am currently figuring out on my rigs if it has something to do with the available performance overhead. For my (weak) rigs, it seems that if the performance overhead is high (because I use the very lowest graphic settings), the less stutter I have. It's a complex problem I think ... and the more I test and read, the more I have the impression that the terrain itself is somehow rated lower to be displayed right in time within the DCS engine. I don't know if my perception is right, but I have the impression that the terrain moves about a certain distance (lets say 100m within e.g. 100 frames), and then at the 101th frame it suddenly "jumps" 20 meters more (where just only one meter more would be good to have it fluent). I know that the position of the aircraft should be at 120m, but why does the aircraft move just 100m within the first 100 frames when 120m would have been necessary? (if you don't understand what I want to ask, ... never mind ... hard to describe at the moment )...

Thank you guys for your answers. Maybe I will make something out of it for the next update ... cu soon!

+1, but please let us decide also in milliseconds (have to use this for some very sensitive X: SET COMMAND() trigger actions regarding pitch trim and roll trim controls.

Guys, I have read the section Roll during g-load on page 271 at least 150 times per day, and I still come to the conclusion that it needs a little rework. I have a few versions (not only these 3) which could (!) maybe explain what the original author maybe had in mind: Version 1: During strong roll input during g-load at low airspeed (Vi < 350 km/h), high roll rates can only be achieved when reducing the g-load. This should not be confused with inverted spin. On the other hand, if the roll input is neutralized, the roll ceases, and the g-load returns to normal values. Vesion 2: During strong roll input during g-load at low airspeed (Vi < 350 km/h), high roll rates can be achieved as the g-load decreases. This should not be confused with a flicked roll. If the roll input is neutralized, the roll ceases, and the g-load returns to normal values. Vesion 3: During strong roll input during g-load at low airspeed (Vi < 350 km/h), high roll rates can be achieved as the g-load decreases. This is similar to a flicked roll. If the roll input is neutralized, the roll ceases, and the g-load returns to normal values. Another question came up for this: Is this behaviour of the real aircraft and how is it modelled / does it behave in DCS?

If you are talking about OpenXR Toolkit: Somewhere I read that the TURBO mode doesn't really turn off ASW, but leaves it running. At least, this is the behaviour of Turbo Mode on both installations of the OpenXR Toolkits on both my rigs ... Turbo mode has no influence on ASW for me.

Don't worry too much about imagination. Sometimes our impressions reveal something wrong, sometimes the impressions are wrong, so ... it's all human factors. You caused no trouble, and many of the questions in the forum - whatever they are about - contain something interesting or something to dig into (again). What really surprised me btw. was the fact that the measured flight data match the data in the permormance sheet very well; this is a really nice fact and therefore thanks goes to the developer!

Very observing, thanks Machalot for this hint! DONE

Hey guys! I did a test flight this evening with latest OB MT, and I have to say that the measured values in the sim fit perfectly to the data provided by Lazybot. I was able to reach M0.77 after 2 minutes 30 seconds flying @15° in 100m altitude with the bespoken loadout. See attached trackfile. 2023-08-18_AJS37_MS_with_X-tank_4xARAK_2xRB24j_2m30s_for_M077.trk

Manuals are usually smarter than the pilot, aren't they??? Regarding a printout: For sure, the next bigger update of RC2.1 will become necessary someday in the near future, but in case you would like to print out a "solid" version (I know it might sound a bit overbearing, but not meant in this way), the current version of the RC2.1 (August 8th 2023) is a version which I personally consider as "not too bad". If you find a minute or two, you may now test on your own, using the data of Lazybot. I am not sure about if I would make it today in the evening to my rig ...

Thank you lazybot, I will use it in the evening, once I have my rig available!

I think you didn't mess up anything. The values you reported seem reasonable, although the 94% seem a bit low. Maybe you can move the throttle just a little more forward, until it snaps in to indicate that the burner range zone 1 is coming ... Regarding the values, check RC2.1 on page 56: null Anyway, I will install an older version of DCS this evening and will test it against the newest version.

Hm, strange. I was able to reach M0.80 using MS at ISA conditions with X-tank, 4xARAK and 2xRB24js, despite - to be honest - the acceleration seems indeed less than before. Version is MT OB 2.8.8.43489. Are you at ISA conditions? 2023-08-18_AJS37_MS_MACH_ISA_with_X-tank_4xARAK_2xRB24j.trk

Good work djacd! *LOL* ... did the same yesterday. I am uploading mine not in a sense of competing, but adding value, for those who like the voice of a "woman" more than a "man" ... Hafe vun! Kind regards, TOViper BASIC_M05__Visual_Landing.miz

With which version are you comparing?

De nada!

yes: 1. in DCS, select the "Display resolution" of your desire (256, 512, 1024) 2. Quit DCS 3. Clear *.fxo cache from user profile 4. Restart DCS and *pray* that it works Post result ...

Think I will put this story to the manual with the next update...

In case the automatic flame-out detector isn't working ... ??

Hey guys! This time, a bit bigger update on the RC2.1b, according to DCS version Openbeta 2.8.7.42583. Hafe vun! Update 2023-08-08: - Added colored text layouts for all warnings (red), cautions (yellow) and advisories (green) (let's see if you like it ...) - Added black/white layouts for designators of - hopefully - all cockpit instruments according to the stickers in the pit (note: this was not done for the checklist section in chapter "5. Procedures" in order to keep these as clear as possible) (let's see if you like it ...) - Didactic references reworked (let's see if you like it ...) - Didactic references are now clickable (click the bold text) (let's see if you like it ...) - Changed text color to grey for all "[no function]" items which are not currently implemented in the module (let's see if you like it ...) - page 24: harmonized terms for certain cockpit elements and labelled some elements with "[no function]" - page 27: corrected numbering (erroneously started the list new with 1, now continues the list with 34) - page 37: reworked distance indicator section a bit - page 59: added picture of the Engine Starter switch - page 69: LT-KRAN EBK switch is now labelled with "[no function]" since it has no function - page 76: added picture of the Emergency Trim panel - page 97: added note for the B-scope (a waypoint in the vicinity of the area of interest is necessary) - page 111: added picture for radar antenna elevation in air-to-air mode - page 114/115: harmonized terms for certain radar controls - page 120: added picture for RWR modes control panel - page 125: changed header "Indications" to "Countermeasures indications" - page 235: reworked "Developers note" - page 236: reworked Engine Start Checklist slightly - page 236: reworked "Developers note" - page 239: changed recommended take-off pitch trim setting to 5° - page 242: added note "0." recommended take-off pitch trim setting - page 251: changed header "Data input" to "Data input / output" - page 297: added picture for Hydraulic pressure fault indicators - page 282: added picture for IR-RB FRAMSTEGN button on left side wall - page 317: added some notes for RB05 in A2G mode - page 354: added some notes for RB05 in A2A mode - page 371: "Output TAKT in mode SPA" is now a header, like "Output TID in mode SPA" - Changed number ranges for better readabilty, like 13,000 - 14,500 kg (many were missing) - Applied at least a zillion small text corrections here and there (let's see if you take notice ...)

Thank you for clarification!

@Zabuzard Can you confirm that ÅTERSTART pushbutton currently has no function in DCS? If so, I would label the switch in the manual with [no function] ... Thanks!

Copy, thought it might be a switch like the HÖJD CI SI switch, which can be held in place. Thanks!

Guys, can you check the notes section on page 317 please, I added the 30 seconds steering command timeframe and the radar behaviour. Thanks! null

Hi Mike, If I understand correctly, the firing of a missile should set the radar to A0 (if it was in A1 or A2). If my assumption is right, then this obvouisly doesn't work in the latest build, since firing in mode NAV sets the radar indeed to A0, but without moving the switch to A0; see track. OB 2.8.7.42718, MT, SP, Caucausus 2023-08-06_AJS37_RB05_A0-A1-A0.trk