corvinus

So true. Bugs are reported on the forum, but they are not organised, prioritised, there is no status for each bug, we cannot vote for it etc. The F-18 has some kind of system going on with status indication in the bug report title and a poll about the next feature to implement, which is a step in the right direction imho. Just having a public bug tracker would help so much. We have a lot of people here bumping threads just to ask attention for their favorite long standing bug. Sometimes developers respond, sometimes they don't. Lack of acknowlegdement leads to customer dissatisfaction, which in turns leads to, well, something not pretty ... :( I believe ED is using mantis as an internal bug tracker. It would be great if a separate public bug tracker could be opened. Just knowing that a bug is acknowlegded or even accepted by a developer to work on, would silence a lot of critique. Being able to vote for a bug would engage the community in a positive constructive way. Just to be clear, this is a DCS wide issue, not just RAZBAM.

Good to hear!

Thanks! That was exactly the purpose I had in mind when creating them.

Remember that the master mode selector and data panel knobs are different from the weapon and interval selectors. The latter have the indications on the knob itself, while the former have them on the panel instead of the knob. The knobs turn just right and natural to me. Honestly I haven't used the TILS (always use the automatic setting), so I can't talk about that one.

That's correct, I checked and the reading corresponds to what it said in the mission editor. Also it corresponds to the way the plane is flying (crab angle). What exactly is changing for you in the aiming symbology? If I press UNSAFE, the reticle just stays in one place. If I approach the target the reticle seems to drift with the wind, so I have to steer the plane into the wind. But it is very tricky to execute and I had no good hits so far. I can't r

Thanks again for the info. It pretty much works as advertised. I had a bit off trouble in the beginning as the keyboard shortcuts for FRAN/INT/KONT were not working, so I had to figure out what the physical positions of the canopy switch represent (I think: norm=fran, mott=int, sand=kont). As it turns out ... the manual explains it pretty well. :book:

Thanks for addressing this issue! Did this fix make it in the patch of last Tuesday? I'm asking because I don't get it to work.

Thanks, I will try this out!

How does it work currently? The only thing that works for me is the "fast countermeasure dispense" button. The KONT/INT/OFF switch near the canopy does not seem to do anything for me.

Thanks for pointing that out! I changed the description (not uploaded yet). Edit: Btw, in mission M07 (Cross Wind landing), the wind was not blowing in the right direction (I had configured the wind at 26 kft to be cross, instead of the wind at the surface :doh:).

Let me know how that works out. :pilotfly: For clarity, the missions are very simple: configure the weapon systems, fly to the target waypoint and deliver the weapon. But there are a lot, so it can keep you busy.

While learning the Viggen module I have been creating small and simple missions. I thought I would organize them a bit and share them with the community. The 70+ missions can be found at: https://www.digitalcombatsimulator.com/en/files/3302241/ These missions are especially useful for people who do not like to use the mission editor. Feel free to use/edit/improve these missions. Description The missions in this mission pack are used to train aspects of the Viggen. They are not tutorials, but more like drill exercises. The idea is to spend as little time as possible on aspects not related to the training objective. For this reason most missions start in mid air. Since weapon employment in the Viggen usually requires some kind of preparation you will be put at a convenient distance from the target area. 1. Take-off and Landing (11 missions) Take-off and landing in clear sky and cross wind conditions. Includes landing on a short runway, a highway and a road. For the latter the surrounding have been cleared for you, so you are not bothered by trees or electricity poles. Also, a ground crew is awaiting you. 2. Navigation (4 missions) A few missions to help practice data input, visual and radar fixes and terrain avoidance. 3. Formation Flying (5 missions) Try to follow your lead in missions of increasing difficulty. The distance between you and your lead is recorded and reported to you. The measurements are used to provide feedback and to assess mission succes or failure. 4. Air to Ground (26 missions) Weapon practice of all air to ground and anti-shipping weapons. For each weapon and weapon employment mode a simple mission is present. 5. Air to Air (7 missions) Weapon practice of all air to air weapons. For each weapon (except the RB-05) you can choose between engaging IL-76MD or MiG-21bis targets. 6. Reconnaissance (4 missions) Practice the SPA and ELINT over sea and land. 7. Countermeasures (15 missions) Get familiar with the KB countermeasures pod and the U22 or U22/A ECM pods. There are escort jamming and self protection jamming missions. For each REDFOR air-defence system there is a mission where you can practice missile evasion. Changelog 1.1.0 2.M05 : New navigation mission for practicing setting time-on-target and ingress speed. 2.M06 : " " " " " " waypoint boundaries (GRANS). 3.M06 : Added targets of opportunity (fuel truck column and a tank column). 7.M09 : Change ROE of SAM site so that they actually engage. 1.0.1 1.M04 : Wind is blowing from South, corrected description. 1.M07 : Corrected wind direction. 1.M09-M11: Fixed ground crew units names in order to make re-arming work again. Added reference points to make coordinate input easier. 2.M02 : Re-added the waypoints that mysteriously disappeared. 4.M10b: Changed description (bomb factory instead of airbase). 7.M01-M04 : Fixed succes criteria./

Don't be sorry, I was not aware of this, but now I am. Thanks.

Great, thanks for the fix! Btw, the manual does not mention a difference between the RB-24J and the RB-74, so you might want to add that to the manual.

O shoot you spoke the R word! Now they have to delete this thread too! PS: Is humor still allowed on this forum? :music_whistling:

What, if any, do you see as the most serious current problems with the Viggen? Let me say beforehand that I'm very happy with the Viggen, it is almost complete and most of the problems are minor. Even during the F-14 development, it still receives attention, which is much appreciated! My top three problems are: IR-uncage is not working https://forums.eagle.ru/showthread.php?t=219138& This effects gameplay significantly in AA missions. KB switch functionality https://forums.eagle.ru/showpost.php?p=3615360&postcount=7 The radar bombing 3km CI cross in misplaced https://forums.eagle.ru/showpost.php?p=3592944&postcount=24 When was the last time you played the module? Yesterday. How great an impact did incomplete/buggy features have on your enjoyment of the module? Not much of an impact as I just switched focus to other weapons systems or weapon delivery modes, but would be very happy if the problems are fixed. Did you raise these issues with HeatBlur? Yes. If so, how satisfied were you with their response, if any. Usually one of the devs responds and the response is always helpful. It is not always clear if the bug is added to their internal bug tracker (which I assume they have). Including the bug report status in the thread title (how it is done for the Hornet) would be a good idea imho. What sort of other important bugs, now resolved, do you remember and how long did it take for them to be resolved? The thrust reverser not working was a bit of a pain, but it was fixed quickly. In your opinion, what is a reasonable amount of time for bugs of varying complexity to be resolved? Two weeks for critical bugs (i.e. bugs that seriously affect gameplay). For other bugs I would say two weeks for trivial bugs (key bindings for example), a month for minor bugs and two months for bugs that require refactoring of code. In your opinion, what is a reasonable amount of time for a module to be in Early Access? 6 months Based on Heatblur's claim of having their F-14B module being mostly feature complete on early access launch, how confident are you they will be able to meet that goal? I'm certain of it. Knowing what you know now, would you purchase the AJS-37 Viggen Module? Yes! Knowing what you know now, would you purchase the F-14 module? I absolutely trust Heatblur to deliver a great F-14 module, so I will probably pick up the F-14, although probably when it is out of (or almost) early access.

There is a bug in the second misson of the Viggen campaign. The load-out consists of 16 high drag bombs and two AA missiles. The latter are loaded under the fuselage. The problems is that the bombs won't release on first trigger press and after that only one bombs is released at a time. It is easy to fix: Go to the mission editor, select the Viggen and select the load-out with 16 HD bombs and two missiles. You will notice that the missiles are now at the outer pylons under the wing. This load out does work as intended. It would be nice if the devs can fix this.

I've noticed in the debriefing that I have a lot of "engine shutdown" and "engine startup" messages, in mid air, that is! It turns out that the "engine shutdown" is correlated with engaging the afterburner, "engine startup" appears when disengaging it. Probably related to this?

I can confirm that overwriting works by entering more than 9 entries. The inability to remove an erroneous result makes it a bit more complicated as you have to remember which entry is valid and which is not. Btw, if I want to select M1 I just select the 1 on the data panel numpad.

:thumbup:

:thumbup:

I also did not succeed in entering the take-off position, but ... entering the run-way heading (and selecting the LS waypoint), does get rid off the NAV.SYST. warning.

For road landings I usually input the landing location and heading. If you, after landing, you switch to BER and then NAV, it automatically selects the correct heading. When I do not enter the L1 coordinates, I enter the runway heading after landing: * BANA/GRANS IN * enter heading (four digits, i.e. 88o enters as 0880) * press LS * switch NAV->BER->NAV Does this work for you?

That's roughly a 20% difference in velocity, so it will certainly make a difference. Glad everything worked out in the end!

Well, actually the Harrier AV-8B carries the Sidearm, which is a short range ARM. Nevertheless, I'm eagerly waiting for the HARM!