FoxxyTrotty

I had something similar happen a couple times during slick wing hi speed transit, coming off the burners and descending (mil power due to speed) I found it extremely easy to break the wings with zero warning. So much the first time it happened I was convinced this was some kinda glitch, but the second time, I wasn't even pulling hard, it was (I'm guessing here) the rapidly increasing IAS as I'm falling down through thicker air. I agree the whole issue needs reworking, and the best approach might well be some kinda roll of the dice. If you over G by 1-2G, basically you're extremely unlucky to have anything go wrong. At 2-4G you wanna be Poppin panels, and anything over thereabouts have a list of things chosen at random that MAY happen.

Situation: Set Caucus map to winter, as its the only one DCS allows to set really cold in winter -12c (i think it was -12.4 but mission brief said -12c close enough)... I put all the warbirds out, cold n dark, and one by one I wanted to test the following, does it start? does it require warm-up? and here are the results for anyone's interest: Caucus, Jan 1, -14c with 5kts wind, turbulence 50, late afternoon. In all tests, I would start up (manual) and immediately takeoff (max 20-30sec for taxi). After takeoff power was set to Max Continuous. Any cooling flaps were used in auto mode (german), or as i deemed as required per temp gauges. All aircraft were flown at low level with max continous for at least 10 minutes before RTB. If there were problems and I had to change anything, it will be documented. Bf 109 K4 - Started only when using cold-start level by the throttle - once it started, no problems. I heard an unusual sound during the takeoff run that soon went away... insane performance. Minor dives were getting 700kmh IAS. Fw 190 A8 - Started no trouble, very strange sound on takeoff - I experienced an immediate loss of power (i guestimate about 50%) which never returned for the duration of the flight - due to the loss of power i had to run at 100% throttle, which it did for the duration. Fw 190 D9 - No problem at all at any stage, no strange noises, and increidbly powerful and responsive in the cold dense air. Mossie - Despite numerous attempts, I was completely unable to get this going in the conditions. P47 - This aircraft was the most interesting, and imo, has the best cold weather modeling... incredibly difficult to start, for those wishing to attempt this, I had to hold down the starter for at least 3x as long as normal, and stroke the throttle up and down as i'm trying to get it to catch without flooding it... Once it started i tried to take off, and immediately siezed the engine just trying to taxi. The oil pressure was reading max without even getting 1,000rpm.... I reloaded the situation and again it took ages to start, this time i waited for it to warm up, because the rpm has to be so low to not get the oil pressure going of the scale, it took even longer to warm up, as it warmed up a bit, the oil lubricated a bit better, the pressure came down a bit, i was able to crack the throttle a little more, which in turn gradually increased the speed at which it could be warmed up... once it was within limits, i took off without further issue - i didn't time the process, but expect at least 5 minutes warm-up and thats if you're willing to nurse the engine as it happens - and much longer if you dont. P51 - This aircraft I didn't even bother attempting to start without a couple seconds of "oil dillute" and then "primer" presses.. That said, it then started fine, and took off instant without any issue or noticeable detriment - that said, the oil pressure was off the charts right away, but there was absolutely no negative impact from having glue-like oil rammed through the system. Spitfire - no cold weather controls to speak of engine wise, I just did the normal start and instant go, and there was exactly like the P51 - zero consequences, and an insane oil pressure readings. Other things of note: All aircraft with oil pressure readings, showed extremely high pressures, as you'd expect. With the exception of the P47, and possibly the Fw 190 A8, there was no consequences at all from jamming this through the engines... I was unable to test the mossie on this. Engine thrusts - I was able to get the highest readings inside the cockpit I had ever seen, be that "boost" or "manifold" or "ATA" - in all cases, minus the A8, the engines produced record breaking amounts of power... Couple that with the thick dense cold air, the props were able to take huge thick dense slices of air as well, mix that together, it was mind boggling amounts of performance, that if anyone saw, would have been the german pilots on the eastern front back in the 1940's. With Mw50 and some climb tests, it was not far from being sabre/mig15 like. Couple this with the massive amounts of grip/lift generated by the wings, it was to make very tight turns and quick sharp moves, especially with the german A8/D9 that was able to exploit the electric trim assists. End of aircrafts report Other thoughts - I would like ED to come up with some kinda standard with regards to the cold weather, and props in general. For example, does oil need to warm up gradually to avoid it forming up bubbles, or not? Does cold weather/icing affect the ability to start an aircraft, or not? While some of things wont matter to some, in any multiplayer environment where a cold-n-dark startup is order of the day, it makes a massive different to hop into a spitfire, or 109 K4 and be in the air inside 60-70seconds, vs say the P47 - which forces you to watch the temps. If you're still reading, well done

yeah it does thats why so many new players fall down inside their own downwash - aka VRS

you know if you look into the whole ground effect thing, and airliners flying 100kts above max speed, it quickly... oh wait, i forgot this ain't conspiracy anon!

the props in DCS are easily the best combat flight sim, flight models available on any game/sim i've test (xplane is not combat sim)... There is adverse yaw, and Nealius is right, you need to get into the settings/special/ specific module/ because by default, DCS has enabled "noob settings" for all ww2 props, namely 100% takeoff rudder assist, and in fight auto rudder. every single prop has these 2 settings and if you disable them, you'll get your adverse yaw and so forth... I made a video about a year back, where i exploited the opposite of adverse yaw (ie i jammed the airlerons so they wouldn't work -option in failures- and used purely the rudder to steer the aircraft around the pattern into land... the same set of forces, from the other side being explloited to achieve this)

I'll add as a long term (5 years) VR user in DCS, this has always been an issue. Its not EVERY aircraft swap, but certainly going in and out of the datalink type ones doesn't seem to help much. The VR frame rate issue (been in forums for years) was described years ago, as i experience, that over time / aircraft swaps, degrades, an on occasion, massively like you describe, cut in half - to resolve this, alt-tabbing out of the game, to ANY other window, for example spotify, click on the window and just do a simple action, i just resize it by any given amount - alttab back into DCS and fps issue is fixed... its done this for years. not sure how or why, when the Ctrl + (numpad 1-5) manipulated DCS/VR options on the fly, it was enough to just cycle ASW off and on, and didnt need to tab out... Anyways, im not adding much other than let you know this is a very long-term issue, and the fix if swapping a/c is a quick alt tab and mess around in another window a few moments and tab back in - beats reloading DCS anyways!

May I just add - It's long been a running theme that RivaTuner (and other GPU overclocking utils) has caused a lot of issues when running alongside DCS (and i think Xplane 11 come to think of it)... To resolve that issue, do the overclock /fan as desired and then quit the tuner BEFORE even starting DCS... no idea why this made a difference, was a huge one for me. I'm very reluctant to mess with the power services, because my system is set to run on low power, both CPU/GPU unless certain apps are loaded, and then clock rates and voltages etc crank up. No need to be running at full/overclock when i'm watching youtube or doing a bit of photoshop etc.. I know some dont mind 24/7 full power, but for me, the heat and such it generates as well as component life (lost a 1080 that way, i'm almost sure of it).

I have a good PC and confirm there's a lag issue with passing groups of planes (not flying with them, but passing them) and if it lags for mine passing 2-3 guys then slightly older hardware i imagine will lag the same with passing (merging) 1 or 2 guys.... Chatting in the AO server i found many to have this issue, but as so many are having other FPS issues, i think this one will get burried under those who are lagging all the time for abit. check forums people are full of lag right now. Hopefully our issues will get resolved also, but what I said aside, at some point the hardware for any PC and any new/updated game will need to catch up. I know it costs a fortune right now, but at least things are back in stock, even at a 30% mark-up, its a lot better than 100-200% a few months ago. Peace

Hey all, In multiplayer I'm noticing a pattern with several others who have decent spec'd machines in VR, 3000series GPU etc that has been a problem since the last update or 2... If you pass a group of 2-3 aircraft (for example a fly by) the FPS go from smooth to 1-2fps for about half a second or so - then normal again... If however you fly in formation with 10 guys, the FPS drop is marginal at worst.... But fly off a minute, and come back.... again a huge FPS hit. Its as if the graphics/textures or whatever is reloading every time. This is on 32gb ssd 3080 setup, and otherwise I dont have the fps issues that many are describing. The FPS hit reminds me very much of the F14 fps hit when you flew past one of those (even if you were in one) back when that came out. Its like it reloaded every time. That was since fixed, but now the glitch seems to happen with all the aircraft. I hope i have given more than enough info to help deal with this and reproduce easy (just join any half busy MP server). Thx

I was doing CAS mission and i got clipped by some AAA and I had the most amazing "damage" to the F18 i had ever experienced in DCS. The engines kept prodcing thrust then cutting out - a bit like compressor stalls, and then instantly all the power would cut out, the engines then came back on, the beeping occured as the systems started to boot up, then again... cut. This actions were repeating every 2-3 seconds, so the there was constant beeping and no functional displays etc. On the way home I decieded to try running the APU, to see if I could milk the power off a working APU to at least get my nav systems working and such - and to my suprise, once the APU had booted up, my systems came back alive. This was such a nice touch and i just really appreciated it and it made me happy, like one of those moments in DCS that I haven't had in a while where I really appreciated the attention to detail - so thanks to whoever put that little gem in.

I think there's still work to be done on how "good" the return on a specific contact should impact the range it is detected, at the moment, there only seems to be a few boolean variables at play and I could of course be wrong, but in practice and hundreds of hours in F18 this seems to be how it rolls: 1) is target in range? 2) is target in LOS? 3) is target above or below horizon 4) is target notching. the first 2 questions outright remove any chance of seeing target, while 3 will reduce max range and 4 will reduce max range even more. When a friend and I was testing the jammer function, it always jammed to an exact range, regardless of anything else - there was no variation by even 1nm if you employed other tactics alongside. I get you'll have some saying it would get infinitely complicated if you factor in everything, but i don't think it has to be. a simple formula that tots up a few scores to give end result

It's realistic that under ideal conditions a radar can detect them, and if the radar is on datalink it will share the info, so yes in a word.

Yep. I just did a cargo mission - the cargo does work, but not having any bindable button makes it very difficult to quickly let go of a hotas to grab the mouse, look down at the collective and press the mouse on the switch quickly before the helo flies into something nearby. This is mega urgent and clearly the controls are wired up and working fine, just needs to be bindable. Also the gun rate Hi / Low option is missing from the binds

But it still works without any impact on performance. Visually its a mess and all bent out of shape. I was happy to see that there was some recognition it had happened though. Until now, only helicopters i had ever had to worry about power lines. Anything else just set power lines on fire, but the aircraft was unscathed. If the P47 prop (other warbirds since yesterdays patch?) is going to get all bent out of shape by flying through the wires (makes sense) then perhaps a huge loss of power, if not total engine failure as well, could be more realistic.

Frustrating issue. ILS beacons do not stop working when the wind picks up or changes direction. So even if we assume the (totally broken) ATC is trying to assign a suitable runway based on the wind, this should have no impact on anyone's ability to tune into a specific ILS, even if it would land them on the opposite direction. ILS for Rw24 is always ILS for Rw24.

Im seeing a lot of posts on this issue, so perhaps a few things to point out for those who might not have flown choppers like Mi8 much 1) Torque. Prop spins one way, it will try to equal and opposite the helicopter the other. 2) Rudder/tail rotor stops this. You need to bind this (ideally to pedals). yes you can use the keyboard, but no not really... pedals is by far most natural 3) even with pedals its still not going straight - the autopilot is broken down into 4 channels (pitch / roll / yaw / blade angles). If you have the YAW autopilot engaged, it will try and yaw into the direction you last timmed it. So if you are in a nice hover facing north, and press trimmer button, the rudder will keep trying to face north. the more you try and fly another direction, and the harder you press rudder to go this other direction, the more gradually the autopilot will keep yawing back to north. to fix this, either disconnect yaw channel (the left most autopilot box) or press trimmer button once pointed in the direction you wish to be. 4) special options / rudder trim [x] - I massively recommend this in DCS heli's, because we dont have physical forces feeding back on our pedals letting us more precisely control the rudder based on where it "feels right". Therefore enable this option, apply as much rudder as you like, press pilot trimmer as normal, and along with the strick being trimmed out to netural, so is the rudder. for those not used to flying helicopters, you need to keep using the "pilot trimmer" to set the forces to neutral everytime you change speeds or power settings, and many times coming in and out of extended hovers and even depending which way into the wind you are facing. This is not to be confused with the regular trim up/down/left/right which does exist on the hind and is an easy way to just add a bit of trim like in a plane. I hope some of these tips help, but dont forget for the autopilots to be working, it needs proper power supply and gyro's etc, so if all the autopilots are not lit up (or stay on red) then you have other issues facing you. I recommend binding autopilot off, trim reset button, pilot trim button, on 1 hat of your hotas and trying to keep it the same across every helo module. Then if rooms allows, I recommend binding another hat on your hotas to the 4 channels of the autopilot. Often times you will just want pitch and bank, other times just yaw. I use the button on the pinky position on the WH throttles for hovering - which already seems to work quite well in hind. hope this helps someone figure something out who maybe new to it all. hope you enjoy it too

For example 1) the cargo controls have no bindings associated with any of the switches in cockpit 2) the autopilot dials have no bindings associated (a increase/decrease is needed for each channel - like in the mi8) note: not refering the autopilot on/off switches, but the spinning dials that you can grab with mouse and spin, or bind in the mi8. thanks

the recommended stuff you are still unable to buy. I had to rebuild my system last december, and to buy what i bought then would cost you 3x as much for the same thing. if you can afford it, go ahead, but i suspect there's a long wait if you dont. If money is no object, then obvious the nvidia 3090. I switched from intel to AMD as their new CPU's were the best gaming CPU's you could buy at the time and the extra cores really help with video editing/streaming kinda lark. I can highly recommend that mix with plenty of SSD across a couple (or more) drives, and 32GB RAM. Ensure you have enough power pack to run it all, and dont skimp on the environmental stuff, like a comfortable chair, solid desk, as they are so cheap vs computer hardware, there's no excuse not if you can shell out 2-3k on a GPU. If money is an issue and you can't afford the recommended stuff, then I dont know what to say. There's shortages all over. My brother in law is manager at an electronics distribution centre for a large company in the UK, and they have massive waiting lists that are getting longer every day for basic components. Some basic stuff to wire a house is 6+ months - and he's at the division level suppling the local shops.

Introduced in this patch is a bug that behaves as follows in multiplayer chat. 1) you press shift+tab to "chat" and type something press enter, the text capture portion of the chat closes and the message goes out. 2) you press shift+tab to chat again, and nothing happens. The chat is shown and then hidden, like you are pressing tab, but the ability to type is gone. 3) you press ctrl+tab to open teamchat, and it works, you type something, press enter, and the message goes out. 4) you press ctrl+tab to add another message, it doesn't work now either... it just opens the existing read-only chat log. 5) you press shift+tab again, and that once again re-opens the ability to enter chat and send it. This pattern repeats indefinitely, and was confirmed by multiple players just now in busy AO server. Secondly to note - When the chat window has focus, HOTAS / pedals are totally locked out, until i either send text message, or escape out of chat window. Until this patch, you could fly with 1 hand, and touch type with the other, sometimes "rgr" or "bs" is very useful and to lose control to neutral can be a big upset.

I have just recreated in the mission editor / single player - and it does not crash the game, but i noticed it was different in another way it behaves: the initial waypoint information instead of reading N0300000 was just blank. Not sure if this helps narrow down the bug or not, but thats it. Thanks

This is another one of those edit waypoint CTD bugs - much like from a couple of years ago that seems to be working its way back into DCS since 2.7 Situation: (everything per instruction / latest updates / no mods etc) Multiplayer (any server/mission) Harrier / Cold start / No Waypoints pre defined in editor (pretty standard setup on many servers) To recreate: Start up and takeoff, all is well. Engage autopilot for ease, and goto map page, data, and the initial waypoint is defaulted to 1. There is incorrect on this waypoint It does not read the spawn point. (it reads something like N030000 - thousands of miles away). I type something relevant in - like the piano keys of the airfield I am using. With Pos selected I press N412345 (for eg) and the second I press enter on the UFC - that's it, boom. I am using VR, but suspect this makes no difference. As this issue has been come and gone for years, there is clearly some critical dependence on this first waypoint, or the variable or memory address it uses, or there's some mix-up or dual use or something that I can't begin to grasp, but clearly something difficult to fix is going on with it. Possible solutions: 1) mission editors to include initial waypoints for harriers. (but are they really going to) 2) make the initial waypoint in harrier inaccessible from the UFC/edit menu, by some arbitrary code. 3) Make some code where if the harrier loads into game and there is no initial waypoint (from mission editor) then perhaps the code for the harrier can auto-generate the first waypoint as though there was one - which could just be spawn point, or 20 yards in front etc. And finally thank you for such a great module. The harrier was brand new when I first started playing DCS and I quickly bought it and have enjoyed it for years, and I've noticed the last 12-18 months more than any other time, it has received a lot of love, with more new weapons and systems added. edit: I am going to see if this bug also happens in single player with the same situation.

This bug is new and causes hard crash with no logs. Reminds me exactly of the hard crash the harrier would do when creating custom waypoints about 6 months ago. Nothing more to say, easy to reproduce

ive just flew the P51 and mig15 and was able to cage/uncage like before to level out the drift

Can I just confirm for the sake of avoiding confusion, that you are not referring to gyroscopic drift here? DCS does simulate the gyro drift, and you must cage/uncage during level flight periodically to level it out. It does seem a little excessive to me in some modules (i know what you mean about easy flight/gentle turns still throws it off) but this is drift, and not some sort of bug that prevents it from being caged. I'll give those aircraft you mention a go and see if I am prevented from caging/uncaging to level out the drift.

this is the case with all mirrors. they are a very low-def version of the scene (i guess to save CPU/GPU cycles). I know what you mean looks bad, so i fold them away and use them only for when tactically essential.