docWilly

I checked instant action/cold start on NTTR. Clean F5E, 100% fuel, weight within limits, trim and approach according to the book (same as you). Result: Even when I touch down gently with around 135 kts it feels like a wobbling landing, aircraft slightly moves to the right, rudder ineffective, chute activation makes it even harder and NWS engagement results in a sudden skid to the opposite direction resulting in a u-turn as described by you. External inspection shows a blown tire right main wheel. That never happens under conditions descibed above on my multiplayer flights. I get the idea that within instant action something is "broken". Winds are not relevant. Do you get this in MP flghts as well? I have really no issues there whatever loadout I have on board as long as weight stays within limits.

Good to know your issue is gone. Happy flying.

Strange stuff, don´t have any issues in MP (2.0 or 1.5). At first it sounds like rudder is linked to throttle somehow in your settings...but you say singleplayer works without that issue??? At least check your bindings again.... Both engines at same power during takeoff roll or is the left one not responding?

I am using HOTAS Warthog (no FFB of course), mapped as well and no issues. I guess it´s related to you "art of mapping", maybe via external Logitech software? Try mapping keys only with the ingame settings, check the action your joystick takes when you klick on trim up/down, maybe it detects your "klick" as an axis, maybe it´s set to "full up/down" on your joystick side. A Logitech user may chime in and offer more help than me.

Dave, I do not experience anything like this. Please make sure a) that your rudder axis is definitely only assigned to your physical rudder and not to any other controls you use (look up settings) b) apply a slight deadzone to your rudder so that minimal physical inputs don´t bother you and maybe flatten the curve to 60% saturation. c) make sure that the behaviour is not triggered by toe brakes (check settings, maybe delete any toe brake asignement) and use instead keyboard "W" (you may assign that to your stick if you can). d) just to be sure: check if there´s crosswind influence At the very beginning I had some issues with my rudders being not physically centered thus resulting in veering over the runway after engaging NWS. Deadzone and saturation down cured that) Willy

Gents, probably you know them already but I thought to link them here would be handy.....hope the sound will be close to the real thing..... Startup and display outside/inside cockpit https://www.youtube.com/watch?v=fIx6frH_WO Sound compilation https://www.youtube.com/watch?v=zz2FpZSgzT4 360 deg video - recommended Enjoy and crank up your speakers! Willy

ZHeN that is correct...I referred to the start of the campaign....but not everyone is so fair to let helos do their work (no offense because that is no given rule). If you have no antenna to deploy something in the wild it´s hard. As soon as you can cover yourself it´s a lot easier

I second Dean´s opinion (concept and work of the Campaing is highly appreciated though). The problem for helo pilots is that if you work on deploying stuff with no CAP cover you are lost - and I am a fairly experienced Huey pilot. Whatever you do - a single Mig 21 will take you down after a while. Well....cooperation - yes....but what can you do if there´s no fighter protecting you. Watch the opposing party do their work. Maybe a "call CAP" option when no human fighter is on your side could be a relief? Dean´s right about the antennas....due to their location and the lack of proper mesh, they are hard to reach...not only because they are really high but no place to put your skids down safely. I was one of the poor pilots destroying the antenna while crashing....placed a Thor but while trying to unpack I was caught by the wind (11m/s) and boom.

should be fixed with todays HOTFIX ( see: https://forums.eagle.ru/showthread.php?p=3243170#post3243170 ) - not tried yet as I am off PC

Jup finch...you are right...as it went public for stable release actually...now I am updating. Anyhow...I started with openbeta and now I have stable release on my PC...whatever I did some months back in fiddling with reverting back to an earlier release...I must have caught a "stable" version. Thank you for pointing me to the right direction

Gents, I tried to update to latest 1.5.7 build today (DCS 1.5.7.9337 Update 2) but it´s not recognized as update and says DCS 1.5.7.8899.335 (my current version) is the one up to date. In forum it´s said that.... "The update will be available today (6 Sept 2017) for an open beta. If no critical issues are found, next week it will be available in the public version. By any chance did my "open Beta" changed to "public" version by one of the earlier updates ??Because I am unable to run the latest update right now.Thank you for an answer. Willy

Refueller speeds Gents, any chance that you gonna have a look into refueller speeds....long known issue in DCS - i know....but currently at least S3-B and IL78 are far too slow to refuel for a fast mover as you are in a speed range where it´s hard to keep up with the tanker. I guess everything works fine at initial start of the mission, but after restarts over time speed degrades to minimum...right? Does anyone know a solution for this?

"glad" to hear I am not the only one. We are both from Europe....maybe #POTUS restricted our connection to US servers :-))) Anyway.....looking for help (and by the way...resetting my internet connection, repair/cleanup and all the usual attempts to find a fix are done without success.

Gentlemen, since yesterday I have the issue that I am unable to connect to your server. After joining there is an eternal "loading screen" and the page where you choose your a/c slot never appears. PC System not changed, nothing newly installed or deinstalled,connection to other servers like 104th, Open conflict etc is fine and not resticted by ping. After a long period it tells me "connection timeout for server ping".... if I "ping" your server it gives me 192ms by any chance...did you set a different restriction for ping to join or othere alterations on server side? Any help appreciated as it worked flawlessly before. Affected are both servers (NTTR and Cauacasus each in latest ED build) Willy

Through the Inferno NEVADA Recently came back to NEVADA Map and happy to find INFERNO there as well. Now my findings flying the mirage and helicopters: Tanker: sometimes on speed, oftern slowing down to around 170 KIAS which is way too slow for refuelling. It´s am long term bug of the missions that tankers tend to behave so and I am not aware if there´s a cure for that. Agressors: on Nevada map it seems most of the time impossible to access the tanker if not a group of blue CAP cleared the area before. Maybe that´s correlated to "initiation of A/A mission" if you spawn in an A/A oriented airframe? Enemy always present? My personal goal would be: refuel fully armed and then go out hunting rather then spending all of your armament and refuel then (if you are still laive of course:music_whistling:) Helos: you have a good chance to be killed before you ever reach the AO....enemies everywhere in the air :-) KA 50 auto-start is broken and I guess it´s a bug on ED´s side. Left engine starts fine, right engine does not. Manual start works. AAA/SAM´s at friendly bases: I never saw our SAM´s to protect for example Nellis.....maybe they ran out of amo? Yesterday enemy F5´s flew low over the base while chasing me on short final.....nothing happened and they disappeared in the sky (observed in late phase before server restart) Crosswind 8m/s: met some other guys heavily struggling with the crosswind at Nellis, in a light helcopter it´s really hard to lift loads or bring the chopper down safely. Maybe a little less wind next time to please more players? Maybe these are some findings that help to improve the mission.

KA 50 auto-start seems to be broken (don´t know if this is a new issue or an old one.... because I recently installed KA50 on this map). Auto-start brings left engine to life but not the right one. Manual starting the right engine thereafter with APU of course works. If you believe it to be an issue of the module, pls look into it. Thank you very much!

Same here, auto-start does not crank right engine with the respective warning in EKRAN. Happens only on 2.1 NEVADA. Solution for now: manual start right engine per manual :thumbup:

Did you try to delete them manually (after backing up before of course)? Should not be too hard to locate thme in the respective folders.

Well I normally don´t like hard words, but the present IC policy let me freak out. At first DCS shows IC green - you think everthing is fine. Then you switch to the Gazelle (and I use the clean glass mod) and it suddenly turns red. Why would "clean glass" be a cheat dear ED? In real life cleaning canopy glass is considered as good airmanship... with all the bugs on your canopy it´s definitely hard to tell if there´s an ememy fighter approaching or just the dirt your lazy ground crew did not clean. But we had this discussion in other threads (now closed).

First question: how did you install it? Did you copy the files into DCS directly or did you use JSGME tool (highly recommended for any mods!!!). With JSGME it´s simple: just deactivate it. If you copied the files into DCS directory and let them overwrite it´s a bit more tricky. First run a cleanup and a repair (guide by SkateZilla....follow the steps....if you are not familiar with cmd lines.....don´t worry...not hard to learn.... https://forums.eagle.ru/showthread.php?t=114030 ). You may also run through this process by using SkateZilla´s tool (link below) If you still get a IC problem thereafter note down the left over files that cause a problem and search for them manually, delete them, then again do a repair, use DCS Updater GUI utility latest build by SkateZilla https://forums.eagle.ru/showthread.php?t=160053 Hope you get along. Let us know. Willy

As per release of 1.5.7 ED considers any texture mod (terrain) as possible cheating (personally as long time 104th texture mod user I do not get why), so they decided to make it fail the IC. There was a discussion about that topic here in the forums to the point the thread was locked. For now: 1.5.7 fly with stock terrain if you are a MP-guy as I am. Superb texture work by Mustang sadly missed.

For joystick user with Warthog Hotas I recommend Central Timmer Mode. Less oscillation, smoother inputs.

AFAIK there´s no downward compatibility in DCS, i.e. if you host with 1.5.6 and a friend has upgraded to 1.5.7 he will not be able to join your server. And furthermore if it´s vice versa it will not work either.

Yes...easily done. But you will notice that - if you are a frequent multiplayer gamer - that popular servers (running 1.5.7) are not available anymore. In contrary to earlier times, you now can not join a server with the latest build 1.5.7. Thats new and part of the IC policy ED runs since last patch to prevent "cheating" with mods (discussion about that here in this forum). So fine for SP but not for MP :-)......had several roll-back´s and - forward´s until I realized what was goin on here. Sadly.

OJ, I know. I already joined as one of the first customers on this topic. The very strange thing is, that for example these Huey cockpit textures PASS IC at first in IC restricted server but after around 40 mins it suddenly decides that these textures are "cheating" and you get tained (happened on Through the Inferno twice). Removing Patos Black Huey textures solves the problem of course...but....I like this CP texture and its no cheating but immersion....and I dont get this ED policy. I followed all the dicussion in the other thread ans I totally aggree with you and Iron Mike. Admins have to decide wether something is IC blocked or not. Simply turning off IC (as suggested by Sith) is not an option as THIS is an open door to cheating. If an admin wants a totally clean DCS server he may run one. Fine. But I go even further....with the new caucasus map there will be again the request to "fine-tune" it = modding....no doubt. And by the way: the thread you mentioned is closed now and you certainly know why :-)