bmbpdk

Hello OnReTech. I assume that when you decided to make a map like the Sinai for a game like DCS World, you surely did some deep research in the area and the "activities" there, especially in the 60´s and the 70´s? And surely you did some research in the airfields/airports and the possible HVT´s in the area? Am i right?

Thank you for the replies guys! And i think its a good thing, it teaches you to dodge and weave when in close proximity of the enemy.

Weird, my Tacview wont show any replay on the map, it just freezes... And i tried re-installing. But thanks for the comment.

I was flying low and at speed over a town in the mission "Gauntlet", when i heard a bang and then an engine and HUD went dead. I crashed and checked Tacview, and as far as i can see i was hit by an RPG! I can load the log in Tacview, but i cant use the map, it just freezes, even though im fully updated at 1.9.0, so i cant actually see the RPG going off. Tacview file have been added. Tacview-20230317-183319-DCS-Gauntlet.zip.acmi

Thank you. Merry Christmas and Happy New Year!

Thank you. So its a real thing and not a bug?

I can confirm that: If i have the RB as a axis (On my Virpil CM3 throttle, the flaps lever), the animation vs input is not synchronised. If i invert the axis in controls/settings, it does not make any difference.

I can confirm that: If i have the RB as a axis (On my Virpil CM3 throttle, the flaps lever), the animation vs input is not synchronised. If i invert the axis in controls/settings, it does not make any difference.

Problem possibly found: 1: I deleted any bind keys and axis for the rotorbrake, in keys and in axis. 2: The engines spools up fine using the mouse to click off the rotorbrake. 3: I binded a button on my Virpil throttle CM3 for releasing the rotorbrake. 4: The engines spools up fine. 5: I deleted the key and binded an axis instead (I used the Flaps lever on the CM3 throttle). 6: I see the animation and hear the sound. 7: The engines did NOT spool up. 8: I recalibrated the axis in VPC interface. 9: Rebinded it in DCS settings. 10: I see the animation and hear the sound. 11: The engines did NOT spool up. 12: In the same session i mouseclicked the rotorbrake handle on and off. 13: The engines spools up. My hypothesis: The rotoraxis goes to 100% when you push it, and then it "relaxes" back to 99%, making the game read the axis movement, but re-reads it as only 99% without reading that as rotorbrake on and without updating the animation. Perhaps there is a wiggleroom of a few percents we arent show in game or there is an inherent axis bug in the CM3 throttle? My advice/solution: DO NOT have axis as the rotorbrake, ONLY buttons or mouseclicks.

Does he by any change have Virpil hardware? I dont know if it matters, perhaps it could be that or the Virpil software, or just a shadow-input from general hardware.

Interesting, there are some similarities yes. Do you know what solution, if any, he applied?

Im having the same issue and reported it a few days ago here:

As some others say, they can easily reproduce this error using the attached track, and its connected to the rotorbrake. It does not matter if the rotorbrake is used through an axis or button, if a different button is used, no change. If the rotorbrake is activated by any other means other than mouseclick, the engine wont spool as other also confirms. When you say "Check your keybindings", what do you mean by that; I cant have anything binded to the rotorbrake, i cant use an axis, i cant use a button?

I just confirmed that: 1: The rotorbrake is the cause. 2: If the rotorbrake is used, either through a axis or a button/key/switch, the engine will NOT spool up, not even if it is moved several time. 3: If the rotorbrake is used ONLY through mouseclick, the engine spools up. Apparently, since no other helicopters have that problem, the Ka-50-3 is reading the rotorbrake wrongly.

Same here, no explanation at all.

I did the following: 1: Created a mission in ME with only me in a single Ka-50, starting cold on the ramp. 2: I did the startup WITHOUT literally touching my hardware; it did start just fine as it should. 3: I did the startup using my hardware´s levers and buttons and switches; no engine spool up at all, only the APU.

Yes its interesting. Ive had the same problems in both cold start instant missions and the training mission. As stated in a previous post in this thread: If i use ANY input from my hardware, the engine wont start as show in the track. But if i ONLY use mouseclicks, no hardware inputs AT ALL, everything works. I will try a usermission in ME right now.

Ground crew have supplied us with a NVG instead of the sight.

Thanks for the help and suggestions. I uploaded the track a few hours ago, before your first post.

As title says.

Yes.

Yes i did, i did as instructed. And apparently the "Wait for 20%" is only for the BS2, since nothing is mentioned here, only to raise the fuel lever.

Very interesting: If i use ANY input from my hardware, the engine wont start as show in the track. But if i ONLY use mouseclicks, no hardware inputs AT ALL, everything works. I disabled "HOTAS SYNC" in the options, just to be sure, even though the instructor said he did. Track file, 16.8MB https://easyupload.io/vwqqv6

I did as told by the instructor and only opened for the number 1 engine. I can make a track for you. Standby.