TOViper

OK! I will fill that time with flying the Cat, and I am looking forward having fun anyway with HB stuff Take your time to make that next Viggen update a good&working one!

Should work like this: Rotate to TAKT Flip to IN Enter 0 Press the respective waypoint button (e.g. B1), Rotate to REF-LOLA Flip to OUT

Pretty high temperature. That's why I was initially asking (2nd post) for the OAT. I remember long time ago that the engine showed oscillations when OAT was high, but currently if you increase the OAT to 50°C the engine dies instantly after spawning into a hot cockpit (considering the throttle position of the real throttle is not synced with the model throttle lever, or it is synced but in the ground idle position). There is a time frame of about ~1 or 2 seconds after spawning for bringing the throttle lever forward to at least flight idle ("flygtomgâng") in order to keep the engine running even at ground. Seems to be a fuel controller problem, but currently I have no idea if this is happening in the real Viggen or not. If I'd consider that OATs above 35°C are very seldom in Sweden, there might be a temperature limit for correct/perfect functioning of the fuel controller at these temperatures ...

Hello Mike! Thanks for your longer answer! Regarding the first section of your writing: I agree what you and your team are working on, making the modules more internally compatible. That's what I would try as well. In the meantime, you should have gotten to know us a bit. We ARE patient, cause we all know about the work necessary for creating such a wonderful piece of software. But at least you have to talk to us! What about just informing us a little bit from time to time (in a pro-active way) about what's happening in the background on the Viggen for us "long time Viggen drivers" ... As the "salt in the soup", this group of enthusiasts on the other side of the production line helped you so much in making this module much more interesting than many other modules around. By simply looking back to 2017 when the Viggen arrived ... you led the way, BY FAR! Now, back in nearly 2022 (!) it's time for your part, by getting rid of ... let me phrase in that way "a few more bugs" , and bringing the beast to a state which would deserve the title "out of early-access". Don't let this happen: "Much good work is lost due to lack of a little more". Please don't overstress our patience and don't play with the long time trust we - still - have in you. We - the biggest Viggen flight sim community - don't deserve that treatment. We rant from time to time, yes, but we were helping many years in making this thing so valuable. Regarding the second section I don't have any great comments. Regarding the third section: I was calling for help sometimes via the forum by using the "@ Username", but to speak in a positive way ... not always I got response Viggen is love. Period. P.S.: Let's to a little test ... @IronMike : I have forgotton to ask: What can we do to help you to help us to help you?

I support the idea of having an independent mission editor, which would be really awesome. One more idea, that came up yesterday after installing a DCS Server on one of my laptops... What about the idea of having a mission editor delivered with the DCS Server? Advantages: .) All maps, all aircraft, all data are already there ... .) Modifying of missions could be easily done on the same machine without using a second computer, fideling around with shares, blah blah ... Disadvantages: .) I don't find any ...

Back to work: this is not fixed. Still got a freeze when going through 90° nose down during a looping. Attached see log. dcs.log

New DCS update log from today: Fixed DCS Crash when looping the aircraft Oh yeah baby yeah baby

I simple removed this module using the module manager, no pop-up appeared again.

Hard to say. If I would make a guess, the standby altimeter didn't work correctly back then and still doesn't, and nothing was changed by HB since 4 years. Maybe they had some more information when programming the instrument, but again I doubt that the standby altimeter should show higher values. If the instrument was not compensated for re-compression, then it must show less altitude. So IMHO there is something wrong with it.

Now, eventually after a few test flights today, I got a LOG file. Single player, engine out, stalling the aircraft and pitching it violently in a strong nose down attitude (around -90° of pitch). dcs.log

If this would be true, the standby altimeter should show less than the main altimeter (higher pressure due to RAM compression leads to higher static pressure > lower altitude indication). No matter of Mach number, the standby altimeter shows the exact same value @M0.3 and @M0.85.

The standby altimeter shows totally different altitude (in case of flying in ~11.500m the difference is ~1500m). Both selected for 1013 hPa. Does anyone have official information regarding the tolerances of the standby altimeter in the Viggen? On the other hand the aircraft wasn't always flying at high altitudes ...

WarbossPetross, this is especially true if you'd fly in VR. On my Rift CV1 I have a hard time seeing them, but on the other hand ... I know where they are and got used to this glitch (as for many other small glitches) If you have your attack point (M.) on the ships, you can rely on the range indicator on the upper right corner of the instrument panel.

For all bugs I noticed I created forum threads, this happend during the last 4 years. From time to time I take a minute, do some test flights, and see if my threads still apply or not (I have a personal list). At a certain point in time this became exhausting due to the slow progress. But after reviewing some threads yesterday, testing a little bit and then talking to a friend who is also flying the Viggen a lot (he is knowing about all my topics) I came to the conclusion that HB is working on bug fixes, which is VERY good. The point was for me, that HB doesn't necessarily fill in the update log, for whatever reason. I just have to go back to my threads and do a little "fixed, thanks" at the end if the thread can be closed if I find a minute on the weekend. For a few I already did, but a few are still missing on this. But don't ask me why I am doing this ... I think it is because I love this module so much and I want it beeing more or less bug free During flying in the last weeks I noticed some little fixes here and there, but yesterday I was in the mood to write that I am not happy with the tempo. This is still true for today, but on the other hand I am glad they do! Just to clear this up a bit ....

Dear Cobra, Thanks for coming into the disussion here, despite I cannot see much that is good enough to satisfy me in total. Hopefully it's just me. I think every one of us (I am talking about the guys adicted to the Viggen here in the forum including me) is aware of the fact that you could spend effort and energy somewhere else. What we are simply not seeing (or at least I do not see) somebody taking care very much of the beast. Examples? Taking care about the new bugs reported since then, or super-short update logs. Your valuable customers are communicating to you in a way you cannot misunderstand, and its very annoying (to me) that there are basic bugs reported and these don't get adressed or even acknowledged. This IS annoying, but moreover disappointing and even frustrating, and HB's behaviour regarding the Viggen these days is away from an (my) understanding of good product maintenance. It might not increase with tyring and exhausting customers, yes ..., but at least you know where you brought us (me) "Viggen lover(s)". If you'd argue the few little things happend the last months on the Viggen code ... yes, that's obviously true, and it is always a nice suprise when updates arrive and us (me) reading (a super-short) update log for the AJS. I was looking forward for new content from HB long time ago, but nowadays ... I just feel bad and sad about what you are (not) doing on the Viggen, and I feel exactly zero motivation for buying anything again from HB. I made a purchase for the F-14 because I trusted you. Trust is subject to change. I REALLY hope this becomes better, and the promised (?) updates are already coded or even in testing phase (ok, ... DREAM_ON_SWITCH released) No ranting, just customer communication within a group of enthusiasts having the same problem. Your sincerily, TOViper Edit (important): meanwhile a humble list arrived on my desk, which shows some bugs on the long list beeing eliminated. OK, so it's just a matter of tempo ... and thus I am happy to eliminate a few sentences I wrote above. Just wanted to let you know ... Edit 2: Cobra, why is HB not adding all the information / repairs to the update log? Wouldn't this help us all?

Cool, thnx mates!

Shouldn't the range marks for minimum and maximum launch range be shown in white color instead of the dark grey? I think this is additional information shown dynamically, depending on the radar range currently set, so I would assume this ... OB 2.7.5.10869 What do you guys think / know about?

Yep, I will give it a try. Which one should I try? https://www.digitalcombatsimulator.com/de/files/3303917/ or https://www.digitalcombatsimulator.com/de/files/3303911/ or https://www.digitalcombatsimulator.com/de/files/3313661/ I'm on 1080ti overclocked with 11GB VRAM, and the effect happend with that graphics card (the same as for my older GTX1070).

As can be heard in this video, the gas turbine starter makes a beautiful noise, which is currently missing in the DCS Viggen. https://www.youtube.com/watch?v=qlap7e3c368

This relates to my computer as well. When I fly the Cat in MP, fighting against F-18s and F-16s, and things become hot (enemy near), the sim gives me 1 to 2 fps for about 2-3 seconds. Total mess in memory/re-load strategy, I already have upgraded from 32 to 40MB RAM.

Currently the afterburner has a little dirty glitch: At closer range the AB isn't shown (my aircraft in F2 view, not AI aircraft!), but a little more far away it is shown. @Cobra847, can you please take a quick look. Attached a picture: Top: from a close distance, AB is not shown Bottom: from a little higher distance, AB is shown OB, 2.7.5.10869, VR

Thanks for that tip, needed this nice little workaround too!

Can't confirm this, since I flew the sorties with mirrors off anyway.

as can be seen in the picture, the KC-135 at take-off shows its light (landing light?) pointing into the skies. MP, OB 2.7.5.10869, Kutaisi

This bug seems to be happening not only on my machine ... at least I am not alone in the dark. @RagnarDa, plz help!! https://forums.eagle.ru/topic/280625-viggen-crash-to-desktop/?tab=comments#comment-4760018