mattebubben

with the 1.5.6 version going into Open beta tomorrow will you remain on the 1.5.5 Stable version or will the server be updating to 1.5.6 (That will include the Viggen)

The 104th have already stated they will be updating to the 1.5.6 Tomorrow (Open Beta Client). And its likely other servers will do the same since this is a major Update and it also bring the Viggen. And again the Store page never said it would not be released on the Open Beta First either, Since they had no way of knowing and there is no reason to think that leatherneck has known it would be released on the 1.5.6 Open beta first either. It works as follow (as far as i understand atleast). 3rd party Devs regularly give ED the latest Versions of their Modules, Then When ever ED is preparing a patch werther it is for Standard Client,Open beta Client or the 2.0 Alpha NTTR client they simply merge those Module Versions into that Update. 3rd Party devs has no control over what goes where when. So Leatherneck simply set a 27th Jan Update with an understanding that ED would make sure there was a Patch that day. But Leatherneck has no say in what type of patch ED decides to make (and whatever they decide to patch will include the Viggen module). And its also unresonable for ED to either Delay the progress on the 1.5.6 patch (if they feel it is ready now) just so we can get the Viggen in 1.5.5 right now or to make all the extra work required to update the Open Beta to 1.5.6 + making a 1.5.5 update just including the Viggen.

Its Raining where i live right now and im pretty sure Leatherneck are to blame. And im very Disappointed in them. #Boycott Leatherneck.

The release is tomorrow. But the ED update (1.5.6) that includes is for the Open Beta Client. So i suggest you change to the Open Beta Client if you want to play it tomorrow. If you want to keep them separated you can download the Open Beta version on its own or there are several guides to show how you can very easily switch between Open beta and Stable (only take a minute or two).

Again This was not Leathernecks Decision... And we dont even know how long they have even known ED intended to make 27th January a Open beta Release so they might have informed us as quickly as they had that info themselves... They said they would have the Aircraft Ready for release for the 27th January they have done so, They cant control what Version of DCS ED puts it into. And with the way DCS is set up Atm every major patch goes into Open beta and if there are no major Problems it becomes Stable a week later. For example the Current Stable Version is the Exact same as the Current Open beta the only difference is that the Open Beta launcher got the Update a Week before the Stable Launcher. So please stop blaming Leatherneck for something that have no control over when they have filled every single one of their promises, They Said the module would be available in 1.5 on the 27th and that promise is forfilled they never specified what 1.5 version (as they have no idea of knowing or controlling that before hand)

1.5.6 is not yet released. Currently Open Beta is using the same version as Stable. Tomorrows patch will update the Open Beta to 1.5.6 and that will bring the Viggen.

Well IRL there were only two types of Liveries carried by the AJ/AJS 37 Attack Viggen in active service. The unpainted metal Scheme during the early-mid 1970s (first few years) and the famous Green Splinter camo for the rest. There were also a few 1-off Paintschemes during the end of its life. There was a Tradition where a Squadron would Paint 1 of its aircraft in a more "eye catching" manor when the aircraft type and or Squadron was being retired one example of that tradition was this AJS 37 And that is a Paintscheme that will certainly be added sooner or later. And we will probably also get some Paint schemes that belonged to other Viggen variants (Low-Vis Grey) as well as some One Of Skins from the other Viggen Variants. They have also confirmed they will do plenty of Fictional skins for the Viggen in use by other nations. And there will most likely also be several Skins for the 2 service paint scheme types for the different Squadrons / Fighter Wings.

Well there are Two types of Pilots in DCS. Aviation Enthusiasts and F-15C Pilots. And if the Aim-54 will be as scary as some fear / think some of those F-15C pilots might emigrate ^^.

This is the only excuse i have ever needed when it comes to afterburner use.

Annoyingly its my Birthday tomorrow. But hey if any Guests decide to show up after the Viggen is released i will simply have to tell them to Bugger off ^^.

I know this Thread has mostly IRL Video of the Viggen but i just had to link this Brilliant video from JiveDilettante showcasing the performance and capabilities of the AJS 37 Viggen. Amazing video that shows off what the AJS 37 Will be capable of in DCS.

Probably depends on conditions. If the pilot was able to quickly re-acquire (also depending on threat situation) he might ripple 2 missiles. But on high speed passes against defended targets it might not be done.

Well you can always Ripple of 2 (or more) Mavericks in a single run. Should not take more then 1-2 sec for each additional missile (selecting the new missile locking on target and launching). So if you start your targeting run from about 14-16 km away from target you should be able to ripple even 3-4 missiles away before you get into the danger zone from AAA etc. That is if you are able to insantly put your nose on the target and dont have to waste time trying to find the target between launches. But even with a longer delay between launches putting just two missiles on target should be no problem in a single pass unless you pop up at a very short range (Or are unable to find the target in time). RB 05A would be different ofc as you cant really guide 2 at once.

As many have already explained it should be very quick and easy to switch to the Open beta Version. You could do it today as its currently using the same Version as the Stable release and then tomorrow it will simply patch as normal and then you will have Viggen. You dont even need to have a Seperate Install if you dont want to.

And while i can also understand it to some degree its completely unresonable for them to blame Leatherneck for it... since its not their fault or in their control... (and they have not borken any promises concerning the release) As the alternative would be to either not get the Viggen or get it but with only more limited Functionality. As its possible some of the New ME Functions (To add Weapon Waypoints for the RB 15 etc) might be the cause for the need for a Beta (together with all the new changes for 1.5.6). Personally i think the reason for the release in the beta form first is simply because that is the version ED had decided to Schedule for this week.

Nothing stated on that page is incorrect though... 1.5 Stable = Caucasus map. and the Viggen release will be on the Caucasus map (I.E everybody will be able to access compared to a 2.0 release where only those with NTTR could get it). It does not Specify what 1.5 version (1.5.5 or 1.5.6) only that it will be a 1.5 release and that is indeed what it is So no Promise has been broken as we will still have a Caucasus release on the 27th... And again To both you and to Magot. Leatherneck has NO CONTROL OVER WHAT VERSION THE MODULE IS RELEASED ON FIRST!!!. That is all up to ED so if you feel like you have to yell at somebody then yell at ED instead of Leatherneck since Leatherneck has no more say in this matter then you do...

Great news =). See you all in there Friday then =).

I find it funny how some people seem to try to blame Leatherneck for this... You guys know this is in no way their fault and they had nothing to do with this change?... Leatherneck (and any other 3rd party dev) has no control what so ever over what Version of the game ED decides to patch. All they do it give ED a version of their module and ED implements that Module into the patch they are making prior to Uploading it. So leatherneck had absolutely NO say in the matter of it being released on Stable or Open Beta its all up to ED... If anything we should just be very grateful Cobra went out of his way to warn us (and we also very possible he was just given this information himself) since this gave us a heads up so we could prepare the Open Beta version. Leatherneck announced the module would be released (into early access) on the 27th of January (and they are keeping that promise) but they had no way to control what version ED decided to patch that day... so i makes no sense what so ever to blame Leatherneck...

But then again with low altitude flying and fast attack runs with minimum exposure time it should still be possible to stay safe enough. Since a proper attack run should only expose you for a few seconds before you can get down low and get away from the target area. This is probably harder in DCS then it is in IRL (due to response times) but should still be doable if one has everything planned out (Does not waste any time after pop up trying to find the target etc but just pop up line up on target launch weapon and then go evasive). Since with the Attack Viggen Speed and low altitude flying is the primary line of defence. And Giving up 1 maverick out of 4 for a Chaff/flare dispenser if you want the added safety of the Countermeasures does not make a huge difference in the long run. So while sure it would be the best of both worlds having those Countermeasure dispensers that dont take up air-ground pylons but it will probably feel like less of a problem once one starts flying / getting used to the aircraft. And when it comes down to it the Attack Viggen is a 1960s / Early 1970s aircraft and for that timeperiod (and even into the 80s ) the Dedicated Chaff/Flare pods were the rule rather then the exception.

Cobra just announced that this Fridays patch (that will Include the Viggen) Will be a new Open Beta Version 1.5.6. And since that is the case will the 104th remain on the stable version until its updated or go to the Open Beta Version to implement the Viggen? I know you usually tend to stay on the Stable version of DCS but will this be an exception (due to the Addition of the Viggen) since i know alot of ppl are excited about the Viggen including allot of 104th players.

Most likely it was a cost / need calculation. They could probably do it without to much trouble but it would cost money and they did not think it needed it for the few more years they intended it to operate as the existing Countermeassure pod was "Good Enough". (And Yes the JA 37 did indeed get the BOL 451 dispensers in the 90s to complement the BOY 401 Flare Dispensers adopted in the late mid-late 80s and both those systems could probably have been adopted to the AJS 37 without to many issues but it was a time period where Cost Saving was one of the most important criteria.)

Mission builders / Servers cant really control the loadouts. They can set the weapons but not the Weapon mixes people decide to use. For me it will depend to some extent on how plausible the alternative loadouts options where. If they could be used but never where or if there were plans to make them useable that were never completed etc. Since the game is already a alternate scenario already so if for example there were changes that were planned but never completed due to the decision to retire the Viggen between 1998-2000 that would have allowed to to carry those weapon mixes then i would be more open towards it. But if its a case of simply adding them for gameplay value im probably not gonna use those mixes. Since in the case of the AGM 65B being added its slightly different since while it was not acquired by the Swedish Airforce it should have been completely compatible with the AJ/AJS so if you simply mounted AGM 65Bs on a standard AJ/AJS 37 it would have been able to use them so in that case im okay with that addition (even if i might not use it much).

Would that future type of combination be realistic or atleast plausible (potential considered upgrade/modification etc). And speaking of that BK 90 + RB 05 combo im guessing BK 90 + RB 75 will also be allowed at that point?. While these additional loadouts would be very useful and you guys are completely free do to whatever you feel best with the module im unsure if i will use those types of loadouts if they are not realistic or atleast plausible but thats mostly because im a history/realism nerd that likes to shoot himself in the foot ^^.

Yea they seem to be dropped from the wrong wing. the CM pod can be carried from either wing (or both) but it was most commonly carried under the Left wing with the ECM Pod under the right (and i think the ECM pod might have been only carried on the right wing though dont know if it was simply procedure or if only the right wing was ECM pod capable.) so it would probably be more proper if they changed the side where the Chaff/flares appear from as the CM pod should usually be carried on the left.

I hope it does not have the Aim-9X since we dont need to advance the timeframe/Weapons further. So giving the F-18 the Aim-9X will make the Russian aircraft Even weaker if it has both Aim-9X and Aim-120s. Id probably prefer a late 90s F-18C since we dont need anything more capable then that (it wont improve gameplay by having a later variant). But since it seems like we are getting a early 2000s variant (With possibly both JHMCS and Aim-9X) i feel like it will very much become the only aircraft flown (by most who own it) since it will be superior to existing aircraft in more or less all ways (A-10C will likely still be better att killing large numbers of undedended ground targets due to its better gun and larger payload). In this way it will have a much greater effect then the Eurofighter since the Eurofighter we are getting does not have Targeting pod ability / Advanced Air-Ground Munitions so it will be primarily Air-Air where as the F-18C will be king in Air-Air And Air-Ground. Since the JHMCS / Aim-9X will make it hands down better armed/equipped then any other aircraft in Air-Air. But if we want to talk hornet we should probably move to a Hornet forum ^^. And Even after the Hornet comes out the the AJS 37 will still be my Nr1 strike aircraft =>. #ViggenForLife.