TOViper

Hello kotor663! I have no idea. As far as I know, they added it to the update cycle, but unfortunately it didn't make the way to the update. I am going to add @IronMike for further investigation.

Hey guys! Right before X-mas, here is another update of the RC2.1, according to DCS version Openbeta 2.9.1.48335. Update 2023-12-18: .) page 050: Added item "EBK zone 1, 2, 3 lights (white digits)." .) page 050: Added picture for showing the KONTR LAMPTABLA button .) page 050: Added picture for showing the KONTROLL button .) page 097: Added detailed explanation and added note for the B-scope (thanks Myse1234 and Machalot, https://forum.dcs.world/topic/331528-radar-mode-a2-doesnt-work-mtst-when-no-waypoint-is-available/) .) page 097: Replaced both pictures with new ones (near Batumi airfield) .) page 235: Added item "Landing gear indicator lights NOSSTÄLL, V STÄLL, H STÄLL lit." .) page 238: Added item "Landing gear indicator lights NOSSTÄLL, V STÄLL, H STÄLL lit." .) page 247: Reworked "After landing" procedure slightly .) page 247: Reworked "Shutdown" procedure (thanks Rudel_chw) .) page 381: Added note for the F-10 map auto-generation-function ATTACK (thanks Discord user mork) Kind regards, TOViper

Hey guys! I am preparing another update of the RC2.1 manual, which (most probably) will be the last one for this year. Plan is to release it before X-mas, since I am super busy in the last week of December and in January. So if you have any issues that I can solve quickly, please send me details, and I will try to take care about. Kind regards, TOViper

Hey Rudel! Thanks for your input! Currently, I am reworking the manual in the procedures section anyway for the next update (before Christmas), so I will go through this procedure as well! Edit: 2 things: a) Why do they turn ON the generator after engine shut-off? Doesn't make sense at first glance, since the normal startup says to turn it on (item 18) b) We don't have the option for checking max ALPHA (neither on the instrument, nor via the DATA panel), so I left this one out (I indeed included the max g-load) Kind regards TOViper

The thumb is a control (clickable device), the indication is an indication. I think you should not focus on the thumb, but on the indication by using trigger condition X: COCKPIT INDICATION TEXT IS EQUAL TO. See DCS Manual page 156. I think the FR22 "indicator ID" might be 30, but I don't know the name for the indication (e.g. "data" or something else).

Thank you!!

The feature that makes this map my favorite one is that it will be the first map for the Viggen. I am looking forward ORBX will create a nice map, and at least I started praying for this a few months ago day by day. I don't want a stutter monster like the South Atlantic map, which I start to abandon because of exactly this.

Thanks Rudel, but I already had this since years, but that was not the point. Yesterday I took a few hours to look in more detail to the graphics.lua. The killers were mirrors set to ON, together with my lower setting for the pre-load radius (usually I used ~50000). I then changed the section CameraMirrors in the graphics.lua MASSIVELY (see below), and increased the pre-load radius to 150000. Now the frame spikes are gone. This is what I use for the camera mirrors. Note that the setting far_clip in section CameraMirrors is IGNORED by DCS totally. You can see landscape in a distance of 50km in the mirrors, despite having the far_clip setting at 1200, therefore no clipping is performed by the graphics engine. I always wondered why the mirrors take so much performance, now I know. thisIsMirror = true; near_clip = 0.02; far_clip = 1200; --structures = {100, 12000}; trees = {100, 1200}; -- looks to be obsolete --dynamic = {300, 12000}; --dynamic2 = {300, 12000,0.5}; dynamic2 = {100, 1200,0.5}; --objects = {3000, 80000}; objects = {100, 1200}; --mirage = {3000, 20000}; mirage = {100, 1200}; --surface = {20000, 80000}; surface = {100, 1200}; --lights = {200, 40000}; lights = {100, 1200}; districtobjects = {100, 1200}; --districts = {8000, 8000}; districts = {100, 1200}; --effects = {10000, 10000}; effects = {100, 1200}; lodMult = 0.5; lodAdd = 0; I am testing further, but the standard DCS settings for the graphics.lua, together with far_clip setting beeing ignored were killers.

Sounds like a good plan. I also use 512 when flying in VR, and at this resolution my 1070 does not go down too much. BTW: in the DCS folder > Config > graphics.lua, I changed the line from TRUE to FALSE: two_pass_always = false; I did not evaluate which setting is faster (or "better"), I am only at the beginning of it ...

Ah, damnit, I didn't have this exact situation I think. I finally switched to 512 or even higher, so I did not have the exact same situation than you. Anyway, Nineline took notice ... which is good!

@Silhou, can you please confirm this bug was put to the tracker, and post the number here? Thank you!!

What I did was making some more free space on the drive with the pagefile (yesterday 14GB, today 28GB free space), and increased the processor speed via the BIOS to 4.4GHz instead of 4.00 GHz (edit: and changed the graphics.lua). These actions made the spikes disappear ...

Ok, thanks for your quick feedback. I am experimenting a bit currently, and I hope I get it sorted out someday.

Hello Rudel! Did you link the correct video? Becaus in this one, I wasn't able to see such spikes, despite one little when still in the air ... I have these spikes during take-off, in air, and the back when landed.

This was solved a few weeks ago, and can be closed.

I have no acces to my higher spec rig currently to look for the logs, sorry. But what I can tell you is, that I sent the mission file to my friend, he opened and saved it, and then I was able to open and run it again. We compared the file "mission." (as part of the .MIZ) with Notepad++, and what we found out was that a few entries (like the date of the mission, and a few other entries) were mixed up in their sequence. Both of us are on Openbeta 2.9.1.48335, but when he saved the file, things then look a bit different in his files than in mine. uff

You can go at 256 or 512 in VR, thats not a big problem, but you have to choose this selection, then quit DCS, then remove the fxo's and let them re-build when re-starting DCS. Did you do that? The point is, every time you change settings, you "must" clean the fxo's. I tell you this, because for my rig, there is no other way around currently.

Hey clanitho! Do you observe frame spikes, where the sim comes to full stop like shown in the screenshot above? The performance - when just looking at the fps, is a bit better in MT, but these spikes make me crazy.

Coming back on the 1070 with my lower spec rig: Intel(R) Core(TM) i7-6700K@4.00GHz GTX1070 40GB RAM @3000MHz Flat screen monitor 1920x1080@60Hz with NVIDA VSYNC set to ON Comparing ST with MT in Openbeta 2.9.1.48335: In ST the performance is pretty fine in ST, there are no frame spikes at all, everything is super fluid (the little spike to the most right is taking the screenshot) In MT things are REALLY bad: During the mission (1 single aircraft on map), spikes at no reasonable times stop the simulation completely for some milliseconds, and it stutters therefore: This is the reason why I still fly in ST. MT is not ready for this kind of configuration. If anybody has tips, I would love to read them. System is configured following all tips & tricks around here. Windows Service Power OFF Windows Graphic Settings HIGH PERFORMANCE Installation on fast SSD with plenty of room for the installation, and the page file on another SDD disk. Again: the ST version runs fine, no stutters!!! IMHO the biggest problem is with MT, nothing else. options.lua

Thanks guys for your quick feedback!! @Machalot: You meant: The B-scope displays a vertical extent about the range of the selected waypoint from -4 km on the near side to +6 km on the far side, and +/-20 deg horizontally. I had to correct this, since its -6 and +4!

Guys, would you be happy with that section on page 97:

This has been reported earlier: https://forum.dcs.world/topic/313962-enabling-spak-possible-in-cold-dark/#comment-5099128

I have similar problems with my super carrier mission that I use for my buddies and me. Last entries of DCS.log before hanging at this point is something with SH-60B. I will try to find a DCS.log on my computer once I have access to it again.

Maybe this little sentence will be going to make into the manual I think. If you allow

This information I think is key.