Spectrum Legacy

You Swedes got some ingenious machinery previously unknown to me! Will have to reconsider my own wishlist... love both the VTOL "de-icer" and "baby draken". Looks so lethal!

It might be that all R60m's are affected, not only Mig21. In L39ZA I do not get front aspect lock tone, but L39 let's you fire anyway even without lock. If you are within specs, you can fire without tone and the head will home in more often than not, even dead head-on if you are really close. This led me to experiment a little bit with Mig21 r60m's and you can emulate it by enabling bomb arm switch (next to the pitot heater switches). You will get "62" green light on and after first launch constant lock tone (which is a bit strange), so from then on you will have to depend on your own judgement when to launch them. Maybe it will help to determine where the issue with r60m's feedback is.

If it was me who made your evening, I'm honestly glad because I know how important a good laugh in the friday evening is after the whole week of hard work! ;) The plane I was trying to trim was in flight though with no effect, yet I do not claim it is a bug, just unfortunate behaviour that after some further testing today I think and hope I can better explain... When you tell a flight-simmer term FFB, he thinks e.g. MS SidewinderFF2 or G940 - i.e. real deal forcefeedback. If you tell FFB to gamer, he thinks xbox/playstation gamepad or some cheaper joystick, i.e. rumble/vibration kind. Unfortunately some drivers for the game hardware are flagged as FFB-capable, despite they do not have motors on axis to create force and move the stick, just vibrate - although it uses the same protocol. Here comes DCS and the implementation of FFB. Let's take the second possibility - joystick with vibration, but not real FFB. DCS detects a driver with FFB-enabled, thus the joystick is expected to behave like full FFB stick, but of course it won't as it doesn't have the real hardware capability to do so. You fly your Albatros, trying to trim it...hat moves, trim tab moves, indicators indicate what they should, DCS sends command via FFB protocol that the joystick should engage the motor on axis to move according to your trim input, but since we don't have the motor there in the first place, nothing happens. Joystick on the table stays in the centre naturally as does the virtual stick in the cockpit. I realised this today after flying Dora, where I had no problem - my gamepad rumbled during hard pulls on the stick and the trim worked fine. All this because the trim in Dora is adjustable horizontal stabilizer which has no effect on the stick in cockpit, thus no conflict in controls... Since there are more people who do have this issues, maybe it would be worthwhile to investigate further and consider some kind of option in the DCS settings along with full ForceFeedback on/off as we currently have and separate "limited ffb" rumble/vibration only on/off (where only the shaking would be transferred, but not the stick forces, axis movement expectations etc). In any case, thanks for reading! Edit & Summary: In the DCS options, I believe it would be helpful, if possible, to have these 3 options that could hopefully clear the problem: FFB off - absolute ffb off, regardless whether DCS recognise device/driver present in the system that is ffb-capable. DCS will not expect the stick to be moved by the ffb motor in any case. Rumble only - limited ffb. DCS recognise device/driver that is ffb-capable but will not expect stick movement by the motor - very similar to the above with ffb off. However the stick will still receive the rumble/shake information for near stall vibration/buffeting etc. Full FFB on - just like we have currently in DCS, for fully FFB capable sticks where DCS expects the stick to be moved by the motor, stiffening, shaking, etc.

I'm also constantly experiencing by this behaviour. Trimmer hat & trimmer tabs move, but stick and plane aren't affected. On my end enabling or disabling FFB in options has no effect. I'm using heavily modified xbox 360 gamepad strapped to my thigh where your kneeboard goes, which acts as rumblepack and 5 axis / 4way hat / 10 buttons controller. Even if I completely clear mapping from that controller and disable ffb in the dcs options, the issue is still present. It seems that the only thing which works is removing the device completely. Flying without trim is pain, flying without early warning vibration/rumble is slightly inconvenient too after you get used to it. For example LNS Mig21 doesn't feature the vibration/rumble at all and the trim works even with the gamepad plugged in. I wonder whether it is mutually exclusive feature...trim or ffb (although simple rumble shouldn't be affected by ffb itself as it is just vibration when shaking occurs).

Rodd, I do ~10 landings a day since the update1 of 1.5.4 in Mig21 and I haven't noticed any difficulties with landing or anything terribly wrong during low speed manoeuvring (<400km/h), although I haven't flown dcs before that for a while (skipped 1.5.3 as the game was crashing for me). The 21 now to me feels similar to 1.2.x when it was first introduced. What I noticed is that ground effect and/or possibly SPS are stronger than in earlier versions though. About responsiveness, can you check that you don't have sau stabilise on? I also remember that after some updates, controls bugged out, until I've rebuilt the config file, especially stick axis assignments. P.S. Check Hadwells landing. He didn't broke the front wheel either - proof of sturdy landing gear indeed! :P

Don't worry, you can get that dx11renderer error and following app crash/hang even on compatible gpu, but it will take some time after mission loads. You might as well give the v1.2.16 build a try (it is dx9 and 32bit), if you just want to check dcs out on your current hardware. Just be warned - it is outdated in many regards.

Yeah you are right, it was C 101! I couldn't find it anymore either... Such a bumma really, one of the best smile-inducing visual bugs I've ever witnessed. It should have been preserved for future generations like a treasure :D Maybe now that we have removable chocks on L39 for example, we can get more of similar and expanded features on other modules as well. The more of these details, the better for greater overall immersion.

Yea, it is my favourite place to do benchmarks for a long time! :D I call it Batumi stress test lol Zooming in your view between those buildings should cause even worse performance. I usually try to aim for such settings, that I never get under 30fps during Batumi stress test.

I think it was attempted more than once to unite the production of variants, as there were quite some variables even on the same model of late war 109s, depending on which parts were available to keep producing the planes. For dogfights I would choose frankenstein G6 latest with most of the neat upgrades and ASM engine. From what I remember, it is pretty much a bit lighter and cleaner G14/AS. Or the all-rounder G10... K4 is one of the heaviest, if not the heaviest late war 109. But one can't go wrong with either of them.

I remember a screenshot a while ago. Calling ground power On would hook up that power trailer to your plane. Someone forgot to request turning it off and took off with it... it was attached to the plane mid air, just like it was on the ground. I'm sure it was some bug in v1.2.x, but the sight of the screenshot still haunts me :D But to your question, cold-start has ground power off as phantom said. It means your systems are running on your onboard battery and onboard apu/starter, where applicable.

You are one very fortunate guy! :D I still have mine...such bumma... Did the crashing stop completely without your intervention, or have you changed / reinstalled something particular? Edit: Ok this time for real, I've managed to stay crash-less for 2 hours straight! :yay: Culprit for driver TDR for me was apparently corrupt windows pagefile. Even though it was set right, it must have had some errors. Found it out when I've disabled the page file completely or changed its size manually to troubleshoot, but even after reboot the file was still there with full 8gb in size. So disabled it, ran safe-mode and deleted it myself from the root, rebooted and re-enabled it with system specific auto-mode again. After that, DCS finally runs on my end. Fingers crossed, it stays that way! :P Edit2: Crashes again, without touching anything. So it appears I just had a lucky run yesterday. I will take a break.

Sehr gut! You guys surprised me with announcements of ww2-related modules not long ago, so can't wait for more of these sneak-peeks. Thanks! Let's not forget... the real men fly ground attack (and highly volatile interceptors)! :prop:

It is not necessary for ground handling, but if you want to fly, you need the booster. Well...I reckon the person in question referred to cold-start scenario, not the weather itself :D If you start hot (with engine already running, or even in-flight) the switch should be already on.

Just a short update on my side, as I've tried dozens of things in the last couple of days. After enabling triple buffering in nvidia control centre or nv-inspector, the crashing of driver stopped it seems, regardless of using v-sync or not, with or without framelimiter. I've also changed pagefile from system managed size (8gb in my case), into complete automatic process. That led to me being able to stay one hour in a very busy multiplayer server for the first time in v1.5.3. It reported 12gb of video memory being used (pagefile usage was around that number too, 10-12gb, despite system set pagefile size reportedly only to 8gb). As expected though, there was some stutter when switching between far planes across the map, but nothing uncommon (ssd only + 2400mhz ram might have an effect on this). Also having shadows at flat-only helped stability, at the cost of no cockpit shadows for now. Will try Mustangs no-tree shadow mod and medium shadows next. Third thing is checking you got pagefile set right. Try those and maybe it will work for you. I will keep testing it further once I get time (spent one week tinkering with drivers, OS, DCS versions, frameworks, utilities and god know what else)! Goddamit! :D EDIT: Alright, back to crashing again. Spectacing seems ok, but flying myself not so. SP mission dropped in 10 minutes with medium shadows and treeshadows-off mod. Without the mod and quality set to flat-only shadows (and flat shadows turned off on the right side of options), it worked ok for about 30min, then crash. Same mission every time (fw190 - dogfight against ai p51 in the instant missions). It's quite random...

Yeah! That's one of the reasons why I trust 21s FM with my life :P I'm sure even Robin Olds would approve the 'stache!

If you have the option, you could give her a spin in v1.2.16 (e.g. via steam - 32bit beta branch is available there). I did so today and ofc 1.2 is inferior to 1.5 / 2.0 in pretty much everything, but man - Dora feels sweet there. Very balanced and pure joyride. So yeah, maybe it is not just that simple in the end as saying that AI just loves to turnfight, therefore 109 is in advantage :P

If 1.45ata is considered low/lowest standard rating here for the K4 (due to wartime shortages of supplies no less or perhaps used by relocation flights with MW50 off), then why stop at that? We can then simulate fuel shortage too. After all, many 109s among other planes were strafed or bombed sitting on the ground, right? Then it would become a ground-quake mission instead. P51 is very decent at strafing though and would fit into the role very well at least until P47 arrives into DCS. Meanwhile I'm travelling back in time, into DCS 1.2.16, to get the feel of my beloved Dora again! ;)

Exactly the same for me, the nvidia driver stops to respond after a while, screen turns black for a few seconds until it restarts while dcs stops to work naturally. What I do is joining random multiplayer server, spectacing other players and eventually it will crash in about 10-20minutes. In the singleplayer it is similar, even in very simple missions with very low unit count and ram usage. I've tried clean uninstall of gpu drivers in safemode with removal utility, rolled back drivers to old ones that were stable in about anything, reinstalled dcs itself into different location while removing the savefolder too before launching it. No joy... It is either caused by some windows update lately, or 1.5.3 is flaky on some systems. So far everyone in the thread is using nvidia, so it might be an indication of driver conflict or perhaps some memory allocation problem on the gpu (as it is always full on 2gb gtx670, with spikes to 2000+mb used out of 2048mb total).

WW2 planes, right? :D The way I see it is that P51 is released, full-feature module with all the available armament options for the variant. Dora has still some small features and details missing, like w-gr.21 rockets, mw50 tank selector, primer pump etc, however it is considered to be out of beta officially. 109 is still in the beta, although I suspect that it's only a matter of time until final FM tweaks will arrive and possibly some kind of short campaign might be added if it has not been already (as was the case with Dora, after which the module got out of beta). I only do have Dora, but I'm trying to stay updated about props and older jets as much as possible... Dora and P51 gets less attention lately it seems, the 109 a bit more. I reckon ED is focusing on the upcoming modules, while fixing the main issues. That's at least my opinion based on lurking too and knowledge-gathering! :P

Found out that changing C6 state of cpu in bios upsets the Mig at least on my system, which will then ask to reactivate. Maybe the info will be of some use...

Well it was mentioned a couple of times before, how the furball mission plays out depending on the AI skill level and planeset. As Jockel mentioned, AI has certain way of flying and some planes fit in this style better than others do. Even with the simple flight model the AI planes are using, the difference shows. As a side note: If the AI stays the same, it will be a real devil in the Spitfire, I'm sure of it! ;)

I'm looking forward to the WW2 goodness! :pilotfly: So take your time...

C and ZA are both part of the same module, or dlc on steam. How to fly in it then you ask? Choose the mission with ZA spawned, or spawn one yourself in the mission editor to check it out.

Just wanted to hop in and say thanks a lot for the Dora videos Little_D! Despite I'm not new to the Dora itself, I still keep watching them now and then. They have that genuine vintage feel and are even relaxing in their own way! :music_whistling: Classy act overall, which I sincerely hope you will finish as a series when the time allows it! Cheers!