Spectrum Legacy

Then nobody would care for their xbox, I reckon. I.e. I don't think we could expect macrosoft to offer highly optimised, lean os for pc gaming, as it would jeopardise their whole gaming console business. In win7 you can fully disable a lot of that bloatware and set it to the point it won't do stuff behind your back, hogging resources (telemetrics, user experience data collection, extensive logging and its sending, auto updates which/when are not needed, various pseudo-maintenance, etc), along with other things like greater freedom in case of drivers, redists, etc,. However macrosoft is working hard to kill win7, so its days are numbered. They don't want another win XP marathon ever again.

What you see in dcs as memory usage is sum of all resources used (combination of system ram, vram and page file on hdd/ssd even if/when vram and system ram gets full). Also it is either not 100% accurate, or dcs was messy with unloading resources after you quit the mission. Where applicable, vram has priority and if your gpu has a lots of it, it will get used (esp. when combining extreme view distance and preload radiuses with high res textures and rendering resolution) - thus more vram is better, faster is better, higher memory bandwidth is better and so on. Imo in almost 2018 there is no reason to buy a card with less than 6-8gb vram, even if you are at 1080p/1440p single screen. Edit: I forgot to ask, OP do you run SLI? Or low speed ram by a chance?

Bird is the word? Blackbird or Super Blackbird confirmed!

Is it a Guppy? Is it a Super Guppy? Ayyy, I hope not! :P

If you don't mind, I will address your comment, despite it was not directed at me. Online activation is just one of the options available for the customer from what I gather. According to Starforce ProActive official webpage, you can activate from a different computer via email or web, or even dumbphone via sms, or fax for example. Neither requires the target computer with dcs installation to be online to access the content. This part is rather important as it is in contrast with the new/upcoming drm, so I would like to underline it. If you base your assumption that starforce drm equals to login/periodical online verification, no doubt you are confusing more people. At the time of purchase, I've checked what I was buying and the following requirements: Incorporates 3rd-party DRM: Starforce ProActive. 10 concurrent machine activation limit. I read on how Starforce works (point system which determines whether your hardware upgrades are extensive to the point where it would count as new unique system, thus warranting a new activation). There is no chance for an average user to be asked to reactivate so many times as to run out of activations. It's safe to assume then, that at least for the majority of users you seem to care about here, this would be one time action per computer and per module, regardless whether it would be online or offline activation. How about the case when requirements for activating and accessing the content or the method of access itself changes post purchase to the point that a customer or a group ends up with inability to access what they paid for, fully or partially(limited access)? Also note that EULA goes right out of window when customer laws and rights are not met, at the very least in the EU, so I wouldn't cling to its every word as some gospel. Playing devil's advocate is one thing, but having snide remarks on top of that about what's bugger won't really help anyone here. But yes indeed, let's wait and see how ED implements the new drm first, since apparently it's already underway and what people think here of it is of secondary concern at best it seems. Somewhat amateurish, but maybe they have serious reasons for the sudden change. Until then, we can only keep pulling at each other's words, guess and assume.

Never heard of that to be honest. If someone has info about it, I would like to know as well. Either it's a misunderstanding, or particular case for some modules which I don't have. I had no popup that would render any module unusable, prompting me to reactivate because the PC was offline for too long, ever. So I can't elaborate. Only special case was the pre-patch mig21, which had issues with starforce and it asked for reactivation even if I updated bios, or enabled/disabled c6 states of cpu in bios, swapped some HID drivers, sometimes seemingly even at random. As of suggestions, I would leave old purchases as they are, potentially with an option for transfer of existing starforce licenses to the new drm, if the customer agrees to it. Such switch would be permanent ofc. All future purchases (even of older modules) would be the new drm already, if ED desires to go that way, as long as it is stated on the store page (which it is now in case of Harrier).

I fail to see how (almost)always online drm equates to starforce drm to some users, while the difference of how it manages your access to products has to be appalling even to laymen. It can be sugarcoated, pulling at words and playing with semantics, it doesn't change a thing on what it is. I consider myself an average user in terms of how often I buy new PC, so one activation per machine was pretty alright for me, esp. since the last activation refreshes itself once a month or so I heard. At steam store page it read: Incorporates 3rd-party DRM: Starforce ProActive 10 machine activation limit. Only one exception where I had to activate more than once was in case of broken drm of pre-patch mig21, but even that didn't deplete the limit on my end. I.e. in my experience it performed how it was advertised/sold and I take starforce as once per machine activation affair (which is no chore to do really, once in a couple of years in my case). On top of it the activation can be done outside of the target PC itself from what I gather (e.g. call, sms, fax, email, web) so your target PC doesn't even need to be online at all for activation. Compare it to (almost)always online drm with direct validation every couple of days, otherwise no joy and possibly shafted customer calling support across the globe during their internet outage (at best, if phone support even becomes an option in this case that is). Despite it might not affect me personally right now at least, the idea is just plain wrong in my opinion and I understand everyone who is feeling slightly miffed by this move. Or is this becoming a MMO now, like World of Warcraft®? I understand always online there, since it's designed as multiplayer-only pretty much, but in this case? Ridiculous...

https://forums.eagle.ru/showpost.php?p=3152146&postcount=19

Might be that the user you are logged in in the windows doesn't have admin rights to change the registry values, or the reboot was not performed (any hibernation/sleep state won't be enough).

Great show guys, I just kicked back and watched the whole thing! Love the L-39. I reckon you all fly with gunsight dismounted and it is just showing it on external model on the alternative camera angles? Just curious, cheers again.

If you have cleaned the Mig21 registry entry by following the instructions or running the reg file, please restart your computer so it takes effect. Afterwards activate the module anew.

@slundal The drm protection changed for Mig21 in the current update. Reason for it is simple: hopefully no more troubles when doing something as trivial as updating the bios of your motherboard, or changing timings of your RAM in the future. So yes, one final headache is here and one action from the user required. If you are willing, I would gladly help you, if you don't feel like searching for the answers in this thread or reading the pdf document instructions (which are pretty straightforward). The whole action takes less work than writing your or mine post here. I certainly would do it for anything I love or am passionate about.

I think P-38 was already as background image on leatherneck website at the launch of Mig21 module in 2014, along with another prop plane iirc, bearcat or something, I don't remember for sure. About next LNS plane, it was speculated for a long time it could be Mig23 because of the similarities in both 3d cockpit model and systems/avionics involved...heck even I speculated about it. I would like ML, MLA or MLD version too (as long as it is the light 23 version), or how about the ground strike variant Mig 27? Or wild dreams 2in1 pack? I would buy! However P-38 J or L is dream plane to fly around too...paired with Corsair it would be splendid. Just like in the airshow video I saw a while ago...

Imo ED really outdid themselves with this module, in terms how the plane feels and handles. Whenever I need something to cheer me up, I fire some L39 flight mission and it helps a lot ... like some sort of therapy! :prop: I grew up among L39s...it's just a pity that my grandfather who was an Albatros (among others) system instructor didn't live long enough to see how flight sims developed in the last 10-15 years. I imagine how cool it would have been to let him fly Albie in DCS if he only was still around, just like your pops is! In any case, you simply can't go wrong with this module. Although the plane is indeed sensitive in pitch as was mentioned already, unless you have stick extension or would use input curvature. P.S. Every plane can be dangerous with a little awacs love and planning. I've seen a couple of F5s that ended up with R60m up in their pipes fired from L39 on cold war server... :music_whistling:

In the take-off sp instant mission (note it has quite some crosswind), the front wheel will burst for me only if I do not rotate at all :dunno: and I keep going full speed down the runway just to see how durable the tires are. Past 300km/h ias the nosewheel will start to bounce and that will burst it. Main wheels lasted to ~400km/h ias, unless I did some wild yawing on purpose, drifting along the runway leaving skidmarks, then the speed to burst them was lower, because of added pressure on one of the wheels. I'm still on 1.5.6.3690 version btw. Normal takeoff procedure mentions to lift the nose around 250km/h (I personally start a little bit earlier by pulling 4/5 stick around 230km/h and as the airspeed builds, I ease the stick to maintain a desired aoa). It feels smoother that way and the plane lifts off nicely. I learned it this way when the module released and it became second nature.

On steam DCS(openbeta) branch we still have the older version 1.5.6.3690 Update 1. Normal/release version is even older I think, before starforce/mig21 patch. Maybe ED will update later steam too this week, I don't know. It depends which version you have...normal/release or openbeta on steam. If it is the release, then my understanding is that's the old 1.5.6.1938 version and old starforce mig21 (you can check the version in main menu of dcs for example, at the bottom right corner). In this case, you should follow the pdf step by step guide in the first post of this pinned thread, deactivating mig21 first and waiting for ED to patch steam release version too, or alternatively opt into openbeta branch on steam after you deactivated the mig module. Openbeta (currently 1.5.6.3690) has the new starforce patch already applied on steam. If you already use openbeta branch on steam and mig works, then all is good. If it doesn't work, you will have to reactivate it. If reactivation fails for some reason (for some users it did), you would have to run the registry deletion/clean which is also mentioned in the pdf guide, restart your pc and then proceed with activation anew. Hope it helps.

No problem for me so far regarding the deploying nor disconnecting the chute (worked every single time so far, with the exception of combat damage). However I've deleted the mig 21 input/config file and let dcs rebuild it from scratch after the update (since I haven't flown dcs for a long time and sometimes those config files acts weird if you skip too many updates and something changed in between).

No worries really, it was fun and also I've managed to bellyland at our base so I wasn't your first official full kill at least :D To be honest I get friendlyfired on often ... as nobody expects albatros and also wingtip-tanks looks like f5 missile rails, straight wings like a10...i.e. it just doesn't look like friend in mig21 which people expect for quick visual ID. Also saw you shot down either a10 or f5 some moments later, so I think you are doing well already. Naturally it's just the first wall of differences and issues when you get into a new module/plane that works different to what you are used and need to practice, adapt and get the hang of it (at least you don't have to relearn the feel for the new FM :P). About awacs, I do use subtitles in the upper left corner of the screen too (I thought they were on by default). I just listen to the first part when awacs calls my number, which I've learned to discern (some numbers are easier, standing out more) and then I check the subtitles for coords. The coordinates provided are relative to you, towards the target, not the bullseye. SA suffers because of the cockpit visibility, but for me also in general dcs, spotting contacts/visibility system is far from ideal. At certain fov/zoom, the models are almost invisible at certain distances depending on lod of the model, and it's always back and forth when lod changes- same old story that was mentioned countless times on forums. True, flying lower than the target is the idea for the radar to work, but not as low as most of the flights at the airquake happens, which are ~250m above ground. At such altitude, the radar is very limited because of the ground return. I don't use piper for IR/gun engagements at all tbh, I have it off. Fixed net for gunning + tone/light for IR. I know that some people use the unrealistic piper following the IR source mode, but I find it distracting - it might help with locating the bandit I guess, if you briefly loose him visually as it disappears for a moment because of reasons (as long as you are within the IR trail). About iff you are right, I do iff at greater distances when I can't identify the contact visually, but for that you have to be at some altitude and/or distance to see the contacts on the radar in first place. Not saying it can't be done though, just the scenario proves decent challenge to most people.

You wasn't useless... you shot me down today! :D Sure I was friendly, but I didn't see you sneaking in and haven't expected that ambush, although I suspected something was amiss on my 6. I don't know what's the difference in awacs between the blue and red, but imo it's quite straightforward for the red. It's just in meters and kilometers. I've also noticed that almost everything in that mission happens very near the ground. F5 just flies its route among the hills near bullseye very low, mig flies over it, afterburner + immelman turn and 9P launch. Rinse and repeat, then rearm at the forward airbase - you can be an ace in one day as long as the mig keeps coming. I guess you can do similar thing with the mig, except the cockpit view is worse + no radar use that low except fixed beam (I assume f5 won't use it much as well, unless they want to tickle you with the guns). Also red awacs is dead quite often, but blue rarely it seems (good grief). It's somewhat stacked against you as a mig driver in that scenario I reckon, but it's just my observation. Also we have to practice more! :P

Thank you for the suggestion. I've managed to find the issue on my end, as I had the throttle axis inverted by a mistake + synchronise throttle with hotas at mission start caused mismatched controls and stuck throttle lever. Once I pushed full throttle instead, the lever would unlock suddenly... then I realised what's going on. :doh: Cheers again!

Thanks guys, I found the issue was on my end after some digging into it. It was "synchronise throttle with hotas controls at mission start" in the options along with inverted throttle axis for the C version by a mistake, which resulted in locked throttle :doh:. Cheers again!

In the current openbeta, are you guys able to put the throttle from stop to idle? In the 'C' I cannot, but in the 'ZA' I can. I've tried to delete the whole control profile for L39C and let dcs rebuild it, but no luck. Just spawn cold/parked L39C in the mission editor, or launch the first training mission to see. Don't know if it's just me or some global issue. Thanks!

First, I would like to thank the team for this update and Starforce issue being resolved (at least for me) at long last since the very release of Mig21. In the past, each time I updated bios, or changed some of the northbridge/cpu related features like C6 states, Iommu/svm, RAM config, etc I would get flagged by Mig21's SF for changing hardware... This behaviour is finally gone in the openbeta (on steam beta branch already since yesterday) - Cheers! P.S. The instructions to deactivate and thus save one activation were pretty straightforward. I'm somewhat surprised that some are having issues with couple of pages long pdf, while as a community we are used to hundred of pages long elaborate manuals in DCS I would think...

Nobody asked about my opinion regarding the engine choice yet, thus I feel offended... deathly so! Haha nooo, seriously now! I'm sure the devs will choose the version they have better access to. I mean the squabble and theorycrafting may just as well continue well into the next year or two, but does it really matter? If you like the plane in question, you will get it regardless of the decision in the end. P.S. Thanks for the sneakpeek of those early polygons - the madame looks lovely! 1st, 2nd & 3rd gen.jets, unite!

External model finished, looking for test pilots to help with the pfm! Any volunteers? :P