fjacobsen

I hope for a DCSW 1.5.6 update as well as updates to the AJS37, M2000C and SA342. Progress for the last two has been incredible slow recently, though the reason has been explained.I care less for DCSW 2.0 I consider to pre purcase the Normandy map but is holding off a bit since it´s not much worth before the WW2 modules has been updated with much better damage modelling.

Any news on this issue ? It´s a long time since it was reported. The way it should work is like on the AJS37 Viggen. Is it just me, or is progress slow on this module ?

I agree At least some kind of status update would be adequite. Don´t get me wrong - I really like DCS, but some modules are only progressing very slowly and focus seems to be more on releasing more alpha/beta stuff than getting issues fixed in the present ones. For me it doesn´t matter whether it´s ED themselves or a 3rd party developer who doesn´t show progress. In my opinion, once they have been paid for an early acces module, they also has commited themselves to get it finished within a reasonable time frame.

It has been quite a long time since last update, which was only a small one at the end of 2016.

+1

Thanks for looking into it !

Not to hijack this thread, but no comment from the devs so far on this, which relates: https://forums.eagle.ru/showthread.php?p=3099485#post3099485

With todays DCSW 1.5.6 stabel, 1.5.6 Beta and 2.0.5 Alpha the RB-15F still seems not to have been fixed. Any comments from the devs ?

With the latest 1.5.6 update the issue with the RB-15F turning 90° appr. 8nm from the target still persist, though the changelog staes that it has been fixed - or maybe another issue than this has been fixed.

Though the "DCS 1.5.6.3690 Update 1" changelog says: "Corrected RB 15 missing its' target" *****Edit***** Seems only Fast mode has been fixed according to this link: https://forums.eagle.ru/showpost.php?p=3097519&postcount=1 *****Edit***** The RB-15F when set to VALB, using 800002, setting Bx8, Bx7 still doesn´t work. The missiles flies to Bx7, turns towards Bx8 (the target(s)) and then appr. 8nm from them turns 90° and offcourse misses- just like pre-patch 1.5.6.

I rather hope for an 1.5 updae. Using the RB04 and RB15f in the Nevada desert does not make much sense. The Viggen is much better suited to be used on the Caucasus map.

+1 I rather want to see the Viggen updated in 1.5 than another buggy 2.0 update where a number of modules no longer works.

And Nevada map since A-10C standalone back in 2011 - if I´m right. Was rejected and put back into fresh developement - but nonetheless same project. I have no problmes with this, byt 3rd party developers should have better opportunities to schedule updates to their products. The AJs37 Viggen has been put on hold for confirmed bugfixes for 4 weeks now. Last fridays introduction of the Viggen to DCSW 2.0 was a nogo for many of us. Regardless I´m probably going to get the Normandy map, but it´s does not always look as focus is on the most important part (at least for us as consumers) to get the available stuff to work as bug free as possible before adding new stuff. m Gem Gem Gem Gem

+1 We have run 3 different versions for ages nw, so an upodate to 1.5.6 would be adequite. According to the Leatherneck devs additional bug fixes has been ready for some time now. Bugger

I really hope for an update today in order to fix the issues with the Viggen etc. in 2.0 - or at least an update for 1.5 to a fix the bugs that has been solved according to the devs of the Viggen.

Seems to be a Starforce problem, so we have to wait on the developers to fix it.

Only if they fix more than they break. Last Fridays updated wrecked a few aircraft as well as introduced the AJS37 Viggen that don´t work in DCS 2.0

I think the pipper tells where the middle of the bomb string will hit. For me Level bombing is quite accurate, though these results where before the drag adjustments in the latest update.

My procdure is: Set Bx8 on the target. Set Bx7 appr. 30-20 km from the target offset to either right or left appr. 20-45°. Set Bx9 behind the target (Bx8) appr. in-line with the path from Bx7-Bx8. Set Bx6 somewhere between my position and Bx7, but closer to my position. When going ANF / ATTACK I have selected Bx8 as navigation point. Launching the RB15F makes them fly correctly to Bx7, then they turn towards Bx8, but then after a few km they turn 90° and miss considerably. This 90° turn does not even point them towards Bx9. As John says - only the 80001 preset seems to work correctly right now. As I told above the user config 811011 also works, attacking separate ships with either missile.

I have now tried all 80000x settings, and only the 800001 seems to work. Using 811011 works great though - hitting two cargo ships. I still need to test the other 81xxxx settings.

Just to be sure... It seems that the only reliable mode to launch the RB15F is still with 800001. Using STD or 800002 will simply make the missiles turn 90° once they are near the targets (appr 8nm / 16km). Has this not been fixed or are all the other modes still WIP ?(no hassle if not - I just want to be sure)

I think stick input as well as excessive trim will override the autopilot. It seems important to properly trim the aircraft for level flight before enganging the autopilot altitude hold.

The M200C dev's should take a look at the DCS AJS-37 Viggen to see how it´s supposed to work.

Great update :) Seems even to include fixes not mentioned in the 27/1 changelog, like fix for the RB15F in STD mode and switching to ATTACK before ANF. Right now the Viggen is my favorite DCS aircraft - there is so much You can do with it.

Why not get drunk together and see who understand what, or if it really matters? As long as we are having fjn together, we don't need alot of conversation :)