TOViper

Update: 2024-01-31, 09:53 UTC Training flights The description for Training flight M190-91 / Simulator Introduction has been modified. It now reads the following: .) Autopilot SA-06: RC2.1 pages 86 to 87 (instead of 86 to 89) .) Flight data unit: RC2.1 pages 88 to 91 (instead of pages 88) Homepage The Quick Start Guide is now downloadable without registration. Thanks Jaccuru for reporting! Have fun guys! TOViper

Hey Rudel! Are you talking about flying in VR or on screen? In VR I indeed had this problem, but on screen I can't remember having troubles seing the flare at 6-7km or even more.

The header of this topic is wrong. It should read "Phinal". Sorry

Hello Jaccuru, thank you for your issue report. You are right, the guide should be public, but currently needs registration. I will repair this very soon. For the time beeing, I attached the guide to the OT of this thread. Kind regards, TOViper

Dear viggen.training user! During the last days (or even weeks, we are trying to figure this out), the LMS Assessment Center experienced a little problem with the payment function. In some cases, the button "Proceed to Checkout" might have been unusable; the button simply didn't change its state from inactive to active. This software bug has been fixed, and you may now proceed with payments as usual. Happy examinations and kind regards, TOViper

I think best would be M0.8 (if you can reach that speed after a pop-up), but I think somewhere I read 10° at least, but I might be mixing that up with something else ...

Hey guys! If I may add my 2 cents on what I see in the video: Too shallow approach, and too slow flying.

Hey Simo! First, thanks for your feedback! Regarding the discord this link, I guess you are right. I created the link by RMB click on the channel > Copy link. But you may use this one here at first: https://discord.gg/heatblur-simulations Can you give me feedback if that worked for you? Thank you!! P.S.: The time-limit was introduced for some different reasons. One technicial is to keep the server clean of "open" flights as good as possible. Another big reason was immersion; to have the student pilots "feel the real challenge"; if he/she starts over, one hour later you are back (this depends on the actual estimated duration of the flight, and will be / is different for most flights), then upload the file (kind of bring back the data-cartridge), then the debriefing comes in. So no time for any breaks or interruptions, just having the pilot stay focussed on the specific flight, fully. This in turn means if someone begins a flight, there is no way out other than cancelling the flight by stopping DCS, and then via the homepage (if your house becomes wobbly caused by an earthquake or something similar ). We want pilots to stay 100% focussed, and we want them to experience each flight as "real" as possible. Usually, there is enough time for uploading the results file. In case you experience short comings on this particular issue, I kindly ask you to provide feedback!

Virtual memory (I am using my M2 drive, since its VERY fast):

Hello guys, I just have a little question regarding the VNE of the M2000C. In the post on page one I can see the VNE graph starting at ~M1.17 (0m, @ISA), which seems to reflect the current behaviour of the DCS module. Where does the VNE graph start for the real aircraft? I'm just curious. Thank you!

lovethewayoumove, Read your story, and something is weird obviously. I will give you a few other tips which I would try out. You may follow them or not, your decision. First: .) Have you ever cleaned your FXO and METASHADERS folders? If not, remove all of them, and let them re-build. Be patient, during the first flights YOU WILL RECEIVE STUTTERS because of them being re-built. Make NVIDIA control panel have them enabled under "Shader cache size" and set to UNLIMITED size. .) De-activate the Windows service "Power" at all. .) In Windows, add a "Graphic setting" for DCS.exe (in the MT folder!!!) for "High performance" (note that the default would be "Let Windows decide"). .) In your computer BIOS, make sure you have C-STATES deactivated (if your bios/cpu) supports this option. .) Make sure Core 0 has no affinity to DCS.exe. .) Make your swap file be fixed in size (e.g. 32GB), on a very fast drive (best is not the same drive as the DCS installation) .) Check your virus scanner and make an exception for ALL folders that could be linked with DCS (install dir, user dir, exports bla bla) Then do the following (if it is not already solved!): .) Try to match the monitor frequency of 60HZ with the situation in DCS: 1. In the NVIDIA control panel you can then activate VERTICAL SYNC > OFF. 2. Make DCS at least run at 80 fps; this means to LOWER YOUR SETTINGS until you hit ~80 fps. 3. In the NVIDIA control panel you can then activate VERTICAL SYNC > ON, and you then should have a good headroom. With that headroom, move up the quality settings in DCS slowly one by one and see what it does. Edit: damnit, I missed one of your posts (https://forum.dcs.world/topic/340089-micro-stuttering-dcs-29/?do=findComment&comment=5355958) ... anyway, I will leave this here, just in case you (or I ... ) missed anything

Thank you Rudel, hope you had happy Christmas too!

Hello Viggen drivers out there! Caused by a bug that I found in the last version (this was in the manual since the beginning), I decided to give you another update of the RC2.1, according to DCS version Openbeta 2.9.2.49629. Update 2023-12-24: .) pages 23-27: Reworked some items, added labels, etc. .) page 25: Item 46 now reads "AFK lever (REGLAGEBROMS AFK) (Auto throttle)" instead of "Throttle friction" .) page 251: Modified the notes for Data input / output .) page 251: Added picture for the data cartridge slot (3D model of cartridge was changed by Heatblur) .) page 251: Modified text for chapter Data cartridge loading Happy Christmas & kind regards, TOViper

I can confirm that the AI Viggen is hovering over ground when spawned on the ramp, see screenshot. Current OB 2.9.2.49629, MT version. @Silhou, can you please confirm it is in the bugtracker? I have to add that this problem exists since a very long time (but I think no one reported it), so it is not a side effect of any new update (at least one year I guess) ...

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