Jump to content

PeterP

Members
  • Posts

    5371
  • Joined

  • Last visited

  • Days Won

    21

Posts posted by PeterP

  1. (sorry if this sounds now arrogant - I heard it often in the last weeks - I just asking for info!)

     

    thanks for coming back- your original info:

    The GTX 590 has 3 DVI inputs only. A splitter perhaps?

     

    My next question after the answer what a "splitter" means for you would be if you can tell if this DVI-D or S ports...

     

    But

    now I know that it has also a Display-port (= equivalent to a DVI-D port)... see - it possible to attach four monitors. ... and you found it out yourself.

     

    splitter ? - for what - getting a dublicate of one of the three possible monitors?

    Well Peter thanks for taking the time to post an answer, now can you actually provide one that might be helpfull? If I knew the answer I would not have posted the question.

  2. Tonight i try again and it works ! But i have a question.which is the difference beetwen rudders control in the axes option and select left rudder and right rudder separately in "all" section ?

    Some time when i leave the foot on the pedals seem to not recenter properly , any tips for that ? Thank you !

     

    A key press for the rudder is a absolute value - means:

    turn rudder to max left/right position until I release the key.

     

     

    A axis is a relative value - means:

    check where I hold the axis and bring the rudder to this point.

  3. ....

    :smilewink::music_whistling:

    ...

    well - no one really uses DCS 1.2.0 seriously for on-line use ATM...

    ...

    So you are good to go with 1.2.0 = about 7 Gigs

     

     

    Installing the modules separate will need about 6 each.

     

    and you will anyway need a LockOn 2 install - as lockon3 isn't released up to now.

     

     

    Choose yourself.

  4. I used the forum-search for 30sec and it spit out this link you may want to read:

    http://forums.eagle.ru/showthread.php?t=52620

     

     

    EDIT:

    TRITATUTTO, I had a look at your join-date and post count...

     

    So here comes my "standard Ka-50 newbie reply" wink.gif:

     

    Read also besides the manual this:

    DCS: Black Shark...

    Technical, Simplified

    -Coaxial Rotor Aerodynamics

    -Trimming the Ka-50 Black Shark <<<!!!! very important to understand this fully!

    -Part 1 - Autopilot <<<this too!

    -Part 2 - Autopilot

     

     

    Interactive training missions:

    KA-50 Black Shark 2 Training missions

     

    And when you still have time , read this too:

    A Stick and Rudder Man's Guide

    to DCS: Black Shark

     

    Here is a useful tweak if you using real rudders:

    How to unchain the rudder from trim - solution

     

    Things you want to have some day too:

     

    KA-50 collective: another picture-tale

     

    Two MS FFB2 with Cougar Grip

     

     

     

    Now there should be (for the next time) no questions left!smile.gif

    Welcome aboard!

  5. No - not in DCS or only when you do big changes in the input-lua files...

     

    Much simpler is to use Autohotkey to program you needed scripts. You can also bind them to a DX controller = joystick.

     

    Here are three "uncommon" examples what Is done with Autohotkey to show you the possibilities. (there is no limit...)

     

    (IMHO - the most capable input-device scripting software on this planet ... much better as target , SST , Xpadder and even Foxy together)

     

     

     

     

     

     

     

    please follow the video info to get more info what exactly it is all about.

     

     

    And what you are asking would look similar like this very simple AHK script file:

    ( what follows after a semicolon is a annotation and has no effect in the script)

     

    #NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases.

    #Warn ; Recommended for catching common errors.

    SendMode Input ; Recommended for new scripts due to its superior speed and reliability.

    SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory.

     

    ; example script for <((((><

     

    $#h:: ; = [win+h] hotkey for follwing action

     

    ; you can put anything you want in it

    ; example for a Joy button:

    ; 1Joy1:: = Jostick ID#1, button #1

     

     

    Sendevent {F1}

    Sendevent {NumPadEnter}

    Sendevent {F12}

     

    ; when [win+h] = F1-->Num Enter-->F12

     

     

    return

    Edit:

    I attached the original AHK file and a 64bit.exe that runs even if autohotkey is not installed at your system as a showcase for you what happens if you press [Win+H].

    • Like 1
  6. So here comes my "standard Ka-50 newbie reply" wink.gif:

     

    Read also besides the manual this:

    DCS: Black Shark...

    Technical, Simplified

    -Coaxial Rotor Aerodynamics <<< This covers also your question

    -Trimming the Ka-50 Black Shark <<<!!!! very important to understand this fully!

    -Part 1 - Autopilot <<<this too!

    -Part 2 - Autopilot

     

     

    Interactive training missions:

    KA-50 Black Shark 2 Training missions

     

    And when you still have time , read this too:

    A Stick and Rudder Man's Guide

    to DCS: Black Shark

     

    Here is a useful tweak if you using real rudders:

    How to unchain the rudder from trim - solution

     

    Things you want to have some day too:

     

    KA-50 collective: another picture-tale

     

    Two MS FFB2 with Cougar Grip

     

     

     

    Now there should be (for the next time) no questions left!smile.gif

    Welcome aboard!

  7. Here is a advise for further troubleshooting/debugging:

     

    Run DCS+Helios (and SoftTh when you like) but this time run a test-track - where you are sure that it will crash after a certain time period - and run this tack again and again but switch a export-device off each time until you cycled through all of your exports.

     

    Maybe there is a bug - and only one Helios export is broken (or a combination of them)...

    Well I know how time consuming this can be... - but this is what " debuggin' " is in the first place :

    a time-vampire :)

  8. Thanks Mustang - I will incorporate it in "Realistic Sun 1.2.2"

     

    But please give me some time - will also have look how to tone down the sun reflection at the water a little bit.

     

    I hope you don't mind when this will take some time -as it is not "so" pressing and there are up to now not so many fast-movers in this altitude operating in DCS-World.

    :)

     

     

    btw:

    would you like to add this to the package PeterP?

    The more important question is if ED will in-cooperate these changes ?!:)

     

    EDIT: Will not include your latest changes to the Sky.fx as it changes significant the look of the sky/behaviour of the HDR when the camera position is near sea level. I think its more important to have a coherent look near the ground as in high altitudes.

  9. Please,please, please :) - tell us a little more about your system and the settings you are using (especially graphic -wise.)

    "2500K OC to 4.5 " really doesn't cut it.

     

     

    A whole DxDiag.txt would be also very helpful beside the GPU/DCS settings.

     

    Here is a wild guess:

    You are using something like TSsAA and MSAAx8 (or even x16)- you are already low on V-ram/recurrences and the extra workload of the light simply kills your system.

  10. Any thoughts?

     

     

    Yes- don't expect that everyone is on 16:9 .

    So: please make it compatible with any common aspect ratio before you upload it- so it will be still round on a different aspect that you are using.

     

     

    Feel free to use the files I prepared for diviplane (but he never uploaded it) as template.

    :)

     

     

     

     

    And for a better compatibility I made presents for all common aspect-ratios of Diviplanes focus.png.

    So the NVG image will always be a circle instead of being stretched when used on a different aspect than 16:9 - as it is right now.

    I added also presents for Triple-head setups.

     

    dive.png

     

    Download pre-sets: http://forums.eagle.ru/attachment.php?attachmentid=60918&d=1325747866

     

    Diveplane,

    maybe you can edit your upload(s) and add these pre-sets.

    and also link the video in your description so everyone is able to customize it to his needs.

  11. Yes - finding the right position can be a time-vampire. But once it is set ... you never have to touch them again - as all works friction less.

     

    I would do it - it's only a small step in the whole building process and you can now reach everything easily.

     

    and don't expect to get them 100% linear - but you can fix it by adding a custom curve later on - so you won't notice.

     

    follow the links - look at the pictures - google from time to time - and you will see how easy it is.

  12. its really straight forward - have a look:

    http://forums.eagle.ru/showthread.php?p=1428398#post1428398

     

    you just have to attach the hall-sensors (about 3€ each) to the axis wires of the fighter-stick controller-board.

    Edit:

    Had a look at your pictures - make sure you have a little longer joint that goes a little deeper in to the Grip - think about that it should last the next coming years - and how it looks now I think that the small plastic pin that holds the lateral movement will brake after some use.

    Don't underestimate the forces you put on it.

  13. 1- I think its answered with the thread I posted - no - I don't think that a counterweight is needed. - but I'm sure you will make your tests how far you can go with the extension.

     

    2 - I found out that I simply could cut the wires to the "dead-man" sensor and it was always on. I added a switch to turn the power on/off when needed.

     

     

    Please look also how the the hall-sensors are attached. I did the same and use this axis in the A-10 and so on.

     

    I use the X/Y of the MSFFB2 only in the Ka-50 because there is a absolute sync between the motors and axis movement needed for trimming properly.

     

    You can neglect it for fixed wing aircrafts -as only the relative position is important for trimming them.

×
×
  • Create New...