sc_neo

Fair enough....sounds good....looking foward to it :)

Issue has been rectified.

So i bought the Red Flag campaign 2 years ago and with the Viggen's RC1 patch this very campaign was added to the module by default. If you own the standalone campaign from before that, you know have a duplicate in your campaign list, and you are wasitng a couple of hundred megs as well. I uninstalled the standalone campaign, but now dcs naggs me on each start to install it again. What can i do? Is there a way how to stop dcs promting me to install owned modules that are currently not installed, or is this something Heatblur needed to change for the Viggen module?

I look at it in reverse: now that we own both blue and red carriers, we can't be charged twice (hopefully) when the new Atc and grew-animation tech will be adopted for the Kuznetsov. It might take a long time, but it would be a total waste to not do this one day. So i have bought the SC module despite not owning the F/A-18 nor F-14 yet, simply to financially support the coresim "Life-things" like ATC, fluid crew, personell and infantry animations etc. I sure hope that that my financial support will help fund that core enhancement so we have better ATC at airports and eventually animated life there as well. We already know that the upcoming civilian flight sim has this in the works, so hopefully ED is encouraged to implement something similar. Develop that for the SC first, then roll that tech out to airports further down the road.

Btw, there is a bunch of "closed" bug reports on the bugtracker that have been closed between 23-25 April, and since there was no OB update since then, there might be actually a substantial amount of stuff coming for the Mig-21 on Wednesday. https://leatherneck-sim.mantishub.io/view_all_bug_page.php?filter=5ec19d1d2206f I hope we get proper and comprehensive patch notes from Magnitude this time.

According to Mr. Grey we might see an up-tick in Mig-21 fixes in the coming months, would be highly appreciated.

Rule number three states; "For an order purchased with partial ED Miles payment, ED Miles are not granted." Meaning if your looking out for making a smart deal, you need to use your miles on a cheaper or heavily discounted module which would not give you a lot of ED miles, and not on a 80$ purchase since you won't get those sweet 10%/8$/8000 ED miles when partially paying with ED miles. Best practice; wait until you have accrued a considerable amout of miles via multiple purchases, and then buy a cheaper module in full (if possible) with those ED miles.

If there was a chance to get the A-4 working with most of the stuff coming with the SC, that would sure make me buy the SC.

@bkthunder I've had a hearty laugh when i noticed you added a "Days since reported" column to the community bug tracker :)

Yep coop would be great!

Actually, all tje instruments, gauges and 3d thjngs are really good and top notch. It is the textures like on the seat and a good deal of the russian turqouise/bluish walltextures that need updating, including the parts of the frame that are hidden under the canopy most the time.

Hrm, i was planning on buying the Mig-21...and i will make that decision at the end of the free month period. But the way it looks now with the dev silence and no way of knowing when the updates will come...i guess i will wait and see how Magnitude operates in the future before buying a module from them.

But is there a timeframe when the new cockpit will arrive? Or is this one of those moments where work will continue only after their next module has been released, i.e. uncertain timeframe of many months or even years?

Did Magnitude state that they intend to code a proper bomb delivery system to replace the fake ccip?

Hey guys, i am thinking of moving up the eastern ladder from the L-39 to the Mig-21. But i have not really kept in touch with the ins and outs of this modules dev. cycle and issues. Yes, it's not EA anymore, but i recall some issues that have been mentioned in the past of which i am not sure which are still a thing. So i'd be interested to gather an overview of what new and longstanding bugs this module has, which features are still missing or are implemented in a simplified way. What i am aware of is the following (correct me if not correct): 1. New cockpit textures are still not available 2. New afterburner look not implemented 3. "Arcady" CCIP bombing mode still present 4. Recently (ED mishap?) FM issues I kinda fear that although this is not EA anymore, if i buy the module now, it still might feel like i might have to wait a very long and uncertain time until the new cockpit arrives for instance. Any ideas when this might be implemented? Any other major bugs?

Actually, i am interested in buying this, but i kinda like to get an idea when the updated cockpit drops before doing so. Is there any place where i can take a look at those updated texture teasers? EDIT: found in the spring update news on the website. Would be cool to get a couple more HD pictures of the upcoming cockpit as an appetizer though!

I was actually pretty surprised that the Ivy bridge cpu held up so well except for a couple of scenarios. Trying to say; the low end is definetly better with a modern high end system, but even then in some situations DCS will make you ask....hell, why did i spent so much money on my rig?

Cool idea and nicely implemented. May i ask; have you actually tested all the bugs in the spreadsheet within DCS yourself lately? I reckon many bugs reports here on the forum are pretty old and it would be important to make sure everything that goes onto that bugtracker is indeed still a valid bug.

Actually, i feel the testphase for each module would kinda make more sense to be 4 instead 2 days long. I, for one, won't have the time and nerve to really take a look at some modules i am interested in within that short of a time window. Especially if one is not in the slightest familiar with the aircraft's operation and procedures. You could make each modules avaialble for 4 days but still keep your 2 day schedule and thus have 2 modules available to test at a time.

i have been wondering and asking about that as well. Still no answer.

@Timghetta Would you say there is a chance for animating the pilot arm, leg and torso movements so it does not block the view to some elements in the cockpit? If no, is that due to the EDGE engine or simply a matter of man power? Because that could a first and unique feature of your modules.

Great to hear, thanks for clarifying this Decoy! Btw, you said before Christmas that you intended to go over the 'Resolved' and 'Problems and Bugs' sections for the Harrier here on the forums and move those wrongly moved reports to the correction section. Have you gone through that already? Additionally, the HUD Velocity Vector is WRONG! @https://forums.eagle.ru/showthread.php?t=222417&page=5 is still not showing up at Razbams official bug tracker, though Zeus stated that work on this bug is happening. It would really go a long way if all properly reported and acknowledged bugs would make it to the bug tracker in a timely manner. That would put many minds at peace a bit i reckon. May i ask, adding those to the bug tracker, is that one of your responsibilites, or is that being done by one of the coders?

Not yet implemented with the Viggen module. Wait for the next big RC patch or buy it in the store if youre on fire.

To be fair, they have stated that fact, DCS being just one of their businesses, more than once over the years. So assuming they would only spent their time working on their three released modules is fallacious. That being said, i would have hoped that the coders would only spent their DCS dev time on those three released modules and not on the F-15 and Mig-23, but there is no way of knowing anyway. When i bought the Harrier it was right at the height when Razbam made some strides on the module in the first half of 2019. I personally realize more and more that EA the way it works in the DCS ecosystem is not really for me, especially if their is not a proper bug -and feature tracker that is meticulously updated by the devs. My willingness to constantly be unsure of whether something is not yet implemented, wrongly or only in part implemented or something doesn't work because it's a bug has grown short. And i bet even the F-14, touted to be fairly feature complete on EA, will have a multi year EA period nonetheless. Once something is released in EA dev. speed seems to slow down, at least that is my impression. At the same time, i have so many modules that i can sink my teeth in at this point, that i really feel no urge to get into half finished stuff anymore. Additionally, it's fine anyway to buy those modules 3-5 years post EA release and drive up the long tail revenue figures a bit.

A post on their discord from Thursday in the bo-105 channel. It's not about being angry but about setting ones expectations straight. Even fairly feature complete modules seem to take ages to get finished. So it's not easy to judge from the state of an EA module on EA release date how long it will take until it is finished and bug free. Especially since every dev. here seems to be working on various modules other than the ones already in EA the entire thing becomes very hard to predict as an enduser.