Jump to content

0xBlb

Members
  • Posts

    21
  • Joined

  • Last visited

Posts posted by 0xBlb

  1. First of all, this is using DCS World 1.2 and corresponding A-10C addon.

     

    I was experimenting with engine start the other day, when I found this... my questions are: is it normal, if yes could you please explain such behavior, if not is it a known bug already?

     

    I followed my usual engine start procedure. After starting both engines, I stood on the brakes, increase throttle to 100% L&R engine power, and cut electrical power (see track for details). Basically at this point, APU is off, APU gen is off, L&R gen are off, inverter is off, battery is off and both engines happily run at full power. Tried to pull L&R engine T-handles hoping it would cut fuel to both engines, but no... both engines still run quite happily at full power.

     

    Why is this?

     

    It is only when I switch battery power back to on than both engine "die".

     

    Is this correct? I remember seeing fuel system schematics on these forums. T-handles should cut fuel, but is fuel cut by an electrical mean or through manually pulling the T-handle?

     

    btw, I cannot find a way to restart my engines after this, are they broken, can you restart them, what am I doing wrong?

     

    track attached...

    a10_strange_engines.trk

  2. Ha, that one was tricky...

     

    The engine starter switch was not released. When releasing it, radio works, engine does not run with ignition switch set to off and temp gauges work fine!

     

    Maybe this is a small bug about the engine starter switch, what I do to trigger this (what I learned in the startup training):

    - ...

    - press and hold engine starter switch with left mouse button

    - when engine starts right click on engine mixture handle (while still holding left mouse button)

    - release left mouse button (engine starter switch stays on, this might be the bug)

  3. Hi,

     

    I've noticed a few strange behaviors illustrated by the attached track. I've got a fresh install of DCS world 1.2.0 + corresponding P51D module.

     

    1. Radio works before starting the engine, but not afterwards... why did it die?

    2. Manifold pressure is higher before engine start than when engine is running idle, is it normal?

    3. Engine can be started, and runs with ignition switch set to off. Is it normal, if yes I would be interested in some (links to) explanations (glider pilot here, knowledge about engines is... stuff for the aero-tow pilot)

    4. Temp, Coolant Temp and Carb. Temp gauges show nothing interesting until RPM gauge reaches 25, then they stop being meaningful when RPM gauge goes back below 22. (I'm playing with this at the end of the track)

     

    Bugs or normal behaviors?

    p51-strange_things.trk

    • Like 1
  4. Can you folks tell me which files i must backup please?

    For me (DCS world under win 7) it is in C:\Users\__my_username__\Saved Games\DCS

     

    Also, can I use the same config file with the settings for the 1.2.0 DCS World and DCS A10 instal, which I will also instal on the new SSD?

    I think I do not understand your question, but one thing for sure: you can't migrate your settings from 1.1.1.x to 1.2... you have to reconfigure from scratch after installing 1.2.0.

     

     

    If you reinstall from scratch, you might want to avoid wasting one activation... please read about "deactivation" here: http://www.digitalcombatsimulator.com/en/faq/activate/ So first deactivate, then format / reinstall from scratch...

    [url=http://www.digitalcombatsimulator.com/en/faq/activate/][/url]

    • Like 1
  5. Several of the download links aren't working for me. It's intermittent which ones will or will not work, but none of them are functional for the P-51D module, and it seems like all of the ftp servers are password locked. Any way to fix this?

     

    It often happens that when an ftp server is overloaded, it denies anonymous access... said ftp server then seems to be password protected, but in fact, is overloaded...

     

    Try http if available or torrents!

  6. If it isnt , why did they (ED) mention that it would ?

     

    Because ED - as many software development companies - sets some deadlines for releases and - as few software development companies - ED is also committed to certain quality standards of their own.

     

    As Wags wrote a few days ago, there are still some important bugs to resolve so they won't release before these get fixed. This is the way I, as a client, prefer.

     

    Your mileage may vary, but I for sure do not want a software released on time that crashes on known bugs every time I try to use it!

  7. nice thats the one i was using so far

    only it didnt work properly

     

    problem was that the button 7 wasnt set as modifier

    now i made it the modifier button so now im able to use

    all the programmed settings !!

     

    Nice!

     

    Be aware that this profile maps joystick+throttle buttons to key combinations. The consequence is that sometimes, if you press two ore more buttons at the same time, a different command is triggered with weird results.

     

    The most annoying I had was throttle stuck at maximum power. In game throttle was reacting to throttle movement, but as soon as I stopped moving the throttle, the in game throttle got back to maximum... very annoying for landing and ground ops!

     

    What I ended up doing is:

    - no profile set in logitech profiler

    - directly map joystick+throttle buttons to commands in DCS: A-10c

    that way, you loose the ability to use the mode selector (on the throttle) but no more throttle to maximum & similar problems...

  8. Have you tried it with teh auto start up?

     

    Never... I always start "manually" and it is the first time this happened. I flew this mission another time and had no problem.

     

    What was your intention? Help me get started (it's ok, thank you) or track the bug down?

  9. Hello,

     

    This might be a bug report, I don't really know... but as this is my first post let me introduce myself.

     

    Yes, first post in these forums although I've been following them quite closely since 9 months approx. I've been playing DCS: A-10C since October 2011, until the beta of DCS: P-51D got released.

     

    IRL, I was a glider pilot, and the detailed flight simulation DCS offers is really something I missed... now I'm hooked!

     

    Sincere and respectful congratulations to the people involved (including the community around) for your hard work. Like many other people around, I'm eager for the next steps in DCS, but I think the strategy taken/described by Wags is a good one and deserves our support. At least I fully support it... that's why I bought DCS: P-51D as early as I could. I intend to do the same for the next aircraft, whatever it will be!

     

     

     

    About the original subject...

     

    I tried the mission Operation Hangover v1.1 http://forums.eagle.ru/showthread.php?t=87854

     

    Before anything else, I switched the battery on and tried to radio the ATC requesting for start-up... and boom, my plane exploded. I tried to have a look at the mission to see if any trigger where implementing this behavior, but found none.

     

    Please find the track attached, this is DCS: P-51D 1.1.2.1

     

    What happened, do you think it's a bug, need more information...

    bug_explode_at_start.trk

×
×
  • Create New...