Druid_

Surge and stall is in. I haven't yet managed to overheat the engine. Maybe some damage might do that but at the moment I am either flying ok or plummeting to the ground in flames :( Along with many things it is being worked on.

When you quit the mission, save the track file and attach it to your post. This way we can verify and recreate.

1. When bugs are fixed a number of things happen. Firstly we have to check that it hasn't broken something else, then the Devs have to merge the fixed code into the latest release version. From what I understand, this is a time consuming and difficult operation in itself. The Dora is a completely different module so won't be linked in anyway to the Sabre patch updates imho. I'd rather patches come out when they are ready rather than rush them out tied to a specific date. 2. Wags already posts an update with the bug fixes prior to a patch or update release. Internally we have access to a list of bug fixes but they may get broken by another fix. The process is ongoing. Providing people with this in real time provides no useful purpose other than to stir things up when things change. 3. No idea on this one sorry.

^correct

Not at all. It might be Sqn specific, year specific or country specific. Therein lies the problem when modelling an aircraft. That's why, when possible, ED will model a specific airframe to start with.

Known issue, reported and being worked on.

Any chance of a reference on this? I can find nothing in our documentation to support this. Range is detected via the radar. You can alter the range manually via the selector. The electrical caging switch does nothing to extend this range as far as I know.

Just so its clear, Mods also relates to any changes you make to ANY of the vanilla DCS files including Helios or anything else for that matter. As testers we do not run any Mods so if you don't do likewise and we can't replicate the problem then it does get a little tricky to narrow down the problem. Glad, you found the problem on this occasion though & GL fixing it.

Mechanically caging is permanent, electrical caging forces the gyro to stabilise. I guess you could manually cage then uncage it, but when pulling say 6G onto the target it would be much better to do so electrically via a button on the throttle grip. First you mechanically uncage it then prior to an attack the sight should be electrically caged to stabilise the sight, limiting gyro deflection as the result of any manoeuvring on initial approach to the target.

Probably got it from somewhere like here

Characteristics of the stall are identical for both. Characteristics of the stall are a slight yawing tendancy approaching the stall followed by an abrupt roll and yaw in either direction. There is no pre-stall buffet. The difference in stall speed for an aircraft with no stores at 13,000lb, Clean and gear down/full flaps is only 10 kts. My tests indicate that the DCS Sabre and the -1 performance graphs are within 2kts. The only error in the stalling speeds is with heavier aircraft carrying stores which I have reported.

Thanks. In a 2 v 1 scenario those migs were desperately trying to lull me into a slow turning fight scenario.

Known bug, in the fix list.

For now yes.

Its not just the performance of the Mig either its AI behaviour that also needs tweaking. Still fun though ...

Circuit pattern & mig 2v1 dogfight.

Sounds like a great time had by all. I wish I lived a little closer in which case I would have pitched up for sure. Maybe next year!

I will take a look into this tomorrow if I get the time. Thanks for bringing it up.

Open the mission in your 1.2.8 mission editor and resave it. If that doesn't work then try any of the single player/campaign missions to check if your DCSW install is ok. If not then re-install. If they work fine and your resaved mission keeps crashing then I can only assume it somehow got corrupted. D_

It may be a case where a memory leak is caused only in specific missions with specific units/scripting/advanced waypoint actions etc. So if you can confirm a mission is giving you a memory leak then please attach the 'leaky' mission to your post so that ED & testers can use it in a testing session and find out the root cause. Thanks.

As a professional pilot myself I can't see myself using anything which puts backlit screens a couple of inches away from my eyes. The long term affects are concerning to say the least. Maybe v.high res OLED or unknown technology screens are better but my concerns will stand until I see a proper study done on any Rift hardware that is released to the public. I'm very impressed by your setup and the quality of your screens. With 2 kids, space in my house is at a premium right now, but at some point in the future I may be in touch. As for Flim's version of immersion... I can think of nothing more immersion breaking than to have to move your goggles up on your head briefly to be able to see a simpit switch or a key on your keyboard.

Many moons ago a RAF jaguar pilot had the canopy cracked slightly open whilst taxiing out for a pairs take-off. When he landed back after a very short flight, his nickname was changed to 'cabriolet'.

I knew there was a problem with HOLD but not HOLD FIRE thanks for mentioning it. I will look into it and raise it with the Devs if its a bug.

What time were you on? Kolkhoz ATC do like to hit the Vodka around 1800 ish.

Iirc use MESSAGE TO GROUP groupname. If it's not in the GUI trigger list then there is a lua equivalent trigger.action.outTextForGroup(GroupId groupId, string text, Time delay)