TOViper

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.

Hey @MYSE1234! I edited my own post above about one hour ago, maybe during the time you prepared your post for jetkid. I cut much of it, since I noticed that I wrote BS. But my picture remains, if you would be so kind and take a look ... its weird. It seems that when the waypoint is behind the aircraft, the A2 mode shows stuff.

Yes, but I think it is helpful to imagine that the radar antenna keeps looking directly onto that waypoint during the time you are passing the waypoint. But this picture KILLS me: I am already 7km away from B2 (I overflew it), B2 is in the opposite direction (after 5km I switched manually back to B2), and the radar starts showing things in front of me. Look at the street at 1 o'clock, which can be seen on the CI as well (its lighter than everything else)...

Update: 2023-12-01, 08:55 UTC Training flights Training flight M190-91 / Simulator Introduction has been modified. It is now interactive, you may use the communication menu for highlighting and finding all the panels. Have fun guys! TOViper

widen76, you deliver outstanding work for us, which is so important for the DCS Viggen. THANK YOU! *May the coffee be with you.*

Hi, thanks for this initiative, however I am also not receiving the verification code (spam checked as well) Contacted you via e-mail and PM.

I actually learned to turn on SSS to have tree and building shadows to be shown (even with setting "Terrain shadows" set to OFF). I also learned that SSS doesn't need big additional performance, which I like. The only thing is, that if you come closer to these objects, the shadows then start disappearing. But above one to two thousand feet they start looking OK.

You are right, this is what I remember too. The way to test this is the following: Touch the Emergency trim (e.g. pitch). Then the normal stick trim should be dead. Then reset the TRIMSYST circuit breaker. Then the normal trim should work again normally.

It is very satisfying to see that the Viggen becomes love, I like it very much. Not only the Viggen as a module, but its pilots too, which is great! There was a squall of tutorials in the beginning, with some more tutorials here and there and now and then, and in 2021. After flying the Viggen A LOT, I felt: ok, let's push it further. This was why I started my viggen.training project in 2021 (indeed back then I started with a big question bank, currently hosting about 500 questions, with the option to increase it to 1600 if the viggen.training project becomes accepted by the community). I took the "short approach", by explaining not too much in the flight itself, but rely on the student pilots reading the relevant sections in the manual (like they did IRL, apart from classroom training). This is why my missions are short, not too much blah blah, only focussing on the hotspot. As I noticed, you are creating everything from scratch, with the aim of giving new users as much information as possible in one go. This enables studying of certain topics in the cockpit, which is another approach. I hope I find the time to go through all of your flights very soon before you publish them, and I feel motivated to help you make them the best in-depth tutorials around. Ah, and by the way: I love Nevada too, and I think I will love Kola even more.

I also enjoy the map verry much, and honestly I can't wait for jumping BuddySpike or similar quality servers onto this map. I just fly around very often, just to look and see ... it's just such a beautiful area. Please guys, don't stop the optimization processes, this map still lacks fps in certain areas/situations compared to other maps.

I am 100% confused about this. Yesterday, in MT with newest patch 2.9.1, I flew with Terrain Shadows OFF, and no shadows of buildings and trees where shown.

Indeed, you have to! There is no way around

Hey guys! Another update of the RC2.1 for you. Update 2023-11-15: - page 019: Highlighted the most important aircraft limitations. - page 154: Moved chapter "Visual landing mode" to page 155 for didactic reasons. - page 246: Changed some text to be shown as WARNING. - page 246: Added "Figure 199: Tr REVAVDR TRANSONIC light illuminated." - page 269: Applied small corrections to the text; changed some of the text to be shown as WARNING. - page 328: Applied small corrections to the RB-04 checklist; added note about separation. - chapter 5. procedures: reworked many items for better clearity/language/understanding/consistency/didactic. - page 233: Changed item 16. text style for ELFEL, RHM FEL and CK. - page 233 + 234: removed items 17. and 20. regarding roll- & yaw trim. (thanks Rudel_chw) - page 235: Added note about limited battery power. (thanks Rudel_chw) - page 238: Removed items 2. and 3. regarding roll- & yaw trim. (thanks Rudel_chw) - page 238: Removed item 6. because fast errection of backup course indicator is not possible. - page 239: Reworked item 2. to include roll trim. (thanks Rudel_chw) - page 239: Reworked item 2. to show yaw trim, but made it appear grey since it is not possible to check yaw trim status (caused by missing yaw trim indicator plug). (thanks Rudel_chw) Have fun! Kind regards, TOViper

Thanks for your kind words guys. Please leave comments on the training flights. I am constantly improving them, and in case necessary I usually repair them very quickly if they show bugs. Just a quick comment from my side regarding the M190:91 / Simulator introduction: This flight is the one and only flight (so far) that contains only Swedish audio ... time to increase your language proficiency ... It is the one and only "flight" in the sim that is not "guided" by an instructor, but is more or less a self-study lesson ...

Really looking forward!

What about talking about the procedure, and then let the student do the steps (and support these by showing the hightlights only and the order to do the step ...)? Could be some sort of "train to proficiency" lesson ...

All in all, and what ever the capacity of the battery is/should be, a rework of normal procedures for the DCS Viggen could be done someday if deemed necessary. On the other hand, 99.956721% of all DCS pilots already have/perform their own procedures/checklists, and they finally become airborne . If you know what to do (and are trained a bit), it takes about 3-5 minutes to complete all steps (depending on what you really need) starting in cold & dark config. IMHO it might be more important to inform pilots about the limits, and maybe give them some rough numbers, and that's it. Situations which require the pilot to start from battery only (without having ground power available) are very seldom, but for exactly theses seldom cases a CAUTION with some little text should be enough ... pilots can read (at least this is what I heard about pilots in general ... )

Sounds reasonable to me (I am not an electric expert )... its just 24V with 37 ampere hours, so if you take 1.5 Ampere for 1 hour, or 3 Ampere for half an hour ... and then the battery is near its end ... (hope I calculated correctly). edit: this calculation was total bullshid. You can take 37 Ampere for one hour, and 74 Ampere for 30 minutes, and about 100 Ampere for 20 minutes. 100 Ampere at 48V equals 4800W, or 4.8kW. Hm. Only avionics take 4.8 kW ... could be?!?! edit2: i tested this, after battery on and nothing else the battery died after 1400 seconds, whereas after 1300 seconds the master warning came up (but with no alert message on the warning panels).

Hey Rudel! Damnit, you spent so much time in preparing good training material, and now it doesn't work as planned. What we maybe could do is - at least to avoid other users from making this mistake someday somewhere somehow at some stage - put this information to the manual. I think it is worth putting this information, e.g. to the procedures chapter for cold start without groundpower, maybe as a CAUTION. How long was the time exactly, and which systems did you turn on (or did not turn on)?