Jump to content

autostart not moving prop- and booster-levers forward.


Recommended Posts

Posted

see trackfile. https://ufile.io/ncjebw6t

  • Like 1
DCS Wishlist: 2K11 Krug SA-4 Ganef SAM, VR-TrackIR icons next to player names in score-chart

PvP: 100+ manual player-kills with Stingers on a well known dynamic campaign server - 100+ VTOL FARP landings & 125+ hours AV-8B, F-14 crew, royal dutch airforce F-16C - PvP campaigns since 2013

DCS server-admins: please adhere to a common sense gaming industry policy as most server admins throughout the industry do. (After all there's enough hostility on the internet already which really doesn't help anyone. Thanks.)

Dell Visor VR headset, Ryzen 5 5600 (6C/12T), RTX 4060 - basic DCS-community rule-of-thumb: Don't believe bad things that a PvP pilot claims about another PvP pilot without having analyzed the existing evidence

  • 1 month later...
Posted

I month and 10 days later, it's still the same.

As long as I remember to move the levers forward before I take off,

otherwise I'm running down the runway wondering why I can't gain speed. :D

🇺🇦  SLAVA UKRAINI  🇺🇦

MoBo - ASUS 990FX R2 Sabertooth,     CPU - AMD FX 9590 @4.7Gb. No OC
RAM - GSkill RipJaws DDR3 32 Gb @2133 MHZ,   GPU - EVGA GeForce GTX 1660Ti 6Gb DDR5 OC'd, Core 180MHz, Memory 800MHz
Game drive - Samsung 980 M.2 EVO 1Tb SSD,    OS Drive - 860 EVO 500Gb SATA SSD, Win10 Pro 22H2

Controls - Thrustmaster T-Flight HOTAS X,   Monitor - LG 32" 1920 X 1080,   PSU - Prestige ATX-PR800W PSU

  • 3 weeks later...
Posted

tried to download the track file: "The hosting period for this file has now expired, only premium users can download it."

However, I don't need the track. The file "Macro_sequencies.lua" under "...\DCS World OpenBeta\Mods\aircraft\P-47D-30\Cockpit\Scripts" defines the start-up sequence. For the propeller RPM it has this line of code:

push_start_command(1.0, {device = devices.ENGINE_CONTROLS, action = device_commands.Button_6, value = 0.0, message = _("Prop RPM lever full forward"), message_timeout = std_message_timeout})

The message says "Prop lever full forward" but the command value is 0.0 which is OFF. For the lever to go full forward, the value should be 1.0.

I don't know what the intent of the developer was, but either the message or the command value should be changed. For the boost lever, the message is consistent with the command value:

push_start_command(2.0, {device = devices.ENGINE_CONTROLS, action = device_commands.Button_9, value = 0.0, message = _("Boost lever to 'Off'"), message_timeout = std_message_timeout})

In my irrelevant opinion, the "OFF" for both axes makes sense. The auto-start should start the plane up so can can go into action. Like a friendly ground crew taking load off the pilot. Managing the engine afterwards should be the pilot's job. So I would just change the message to "Prop RPM lever to OFF".

  • Like 1

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...