Jump to content

Rockrend

Members
  • Posts

    93
  • Joined

  • Last visited

Posts posted by Rockrend

  1. When I say "joystick controller", I mean it in terms of the name Windows gives to a devices like this, as opposed to an actual joystick.  So long as you can get the switches, potentiometers and encoders, it can be done very easily.  Additionally, you can definitely set Pro Micro's with unique identities.

    Hope this is helpful. 

  2. 2 hours ago, durka-durka said:

     

    My goal is to make a small panel of switches in the F-16. Top Left Panel: 

    • 1x Laser Arm (on/off)
    • 1x Master Arm (on/off/on)
    • 2x Autopilot function switches (on/off/on). 

    I'm pretty confident I can wire the switches up, but I feel like getting it to work in DCS is over my head, or I'm just overthinking it.  What's the best way to go about this?  

     

    14.JPG

    Hi,

    I've used Arduino's to build a range of button boxes, so you can definitely do what you want.  As per previous advice, no need to use DCS-BIOS, just use the Arduino as a "joystick controller".  See the YT link to get an idea of how to make the connections and the sketch you will use to control the device.  He is using it for a car racing game but the principle is exactly the same.  Good luck.  

     

  3. Hi all,

    I've noticed a problem with CA in version 2.7.11.22211.  When I switch to isometric view using the insert key and try to move the turret on MBT's (this is all I've tried so far) using the arrow keys, the turret doesn't move (it used to).  I can however, move the turret with the mouse in isometric view.

    Everything works as normal in gunner view (turret moves with arrow keys and mouse) and when I switch to external unit view using F7, just not when switching to isometric view by using the insert key. 

    In the attached track, you can see the turret trying to move and jerking around a little in isometric view and working normally in gunner view.

    Any assistance would be appreciated.  I have also done a slow repair, with no change.

    CA test track.trk CA Test.miz

  4. I'm seeing exactly the same behaviour from the Lightning II pod as well.  It's OK when the image is zoomed out and there is a black border around the image but as soon as you zoom in, the diamond becomes very hard to see, as the green scale image becomes larger and the black border shrinks.  As per the OP, this happens regardless of the contrast or brightness setting.  Pls let us know if you require more info or screenshots.

     

  5. 13 minutes ago, NineLine said:

    Ok, I was able to reproduce it and boy what a nasty crash, I will get it reported ASAP, thanks for all the help and patience. 

    Excellent...yep pretty nasty crash alright.  Thanks to all that contributed.

    If it's of any use now, 32G RAM, i7 6700k (stop laughing), MSI NVIDIA RTX2080 Super, Win10 (latest version and current update), DCS is on a 1TB Samsung SSD, Win10 is on a 1TB M2 SSD.

    • Thanks 1
  6. 3 hours ago, NineLine said:

    Can you just attach the file, I deleted the full log, it kills the thread, sorry.

    Here it is.  The crash is at the end of the log and it also shows some successful loads of the same mission, prior to the crash.  The mission is also attached.  No mods or edits and I also tried a slow repair.  As I said, the crash doesn't always happen and I haven't been able to identify what exact action precedes the crash on my part either.  Hopefully the log and mission will shed some light on the subject.

    Thanks...   

    dcs.log.old FW 190 A-8 Takeoff.miz

  7. 1 hour ago, LeCuvier said:

    Please do not paste the text of a logfile directly into the post! Just attach the file. Nobody wants to scroll forever just to find the next post.

    My apologies…For some reason I couldn’t find the attach file button at the time of posting. Thanks very much for your input, it is appreciated. Hopefully your information will cast further light on the cause of the crash.

  8. Just recently my Anton has been crashing DCS upon hitting "fly".  It doesn't do it all the time and I can't seem to identify exactly what circumstances lead to the crash.  Please find the log and mission below...https://forums.eagle.ru/topic/292315-anton-crashes-dcs/?do=findComment&comment=4884921

    Possibly something to do with the sound, that seems to be the last thing that happened before the crash.

     

    I'd appreciate some assistance or insight into the cause.  Thanks...

     

    • Like 2
  9. There would have been a range of navigation beacons located all over that part of England during WW2, all with different frequencies and Morse idents.  Also, each airfield would have been likely to have several navigation beacons in its vicinity at different times. You may actually find it’s easier to just setup your own. If you want the current details for airfields in 2021, the UK AIP can be found at www.caa.co.uk

  10. Hi all,

    I'm using DCS Stable 2.5.6.59625.1 and have noticed a possible problem with the AGM-84E cruise altitude profile setting.  What ever I set the cruise altitude profile to (high, medium or low), after launch, the missile will always try to maintain the original launch altitude for the cruise phase of it flight, rather than the selected high, medium or low profile.

     

    I've included a track to show a launch from ~25k ft, with the cruise profile set to medium (15k ft).  You will see that the missile attempts to cruise at the original launch altitude, rather than 15k ft as per the profile setting.

     

    Is anyone seeing the same behaviour and can this be checked by ED please.

     

    Thanks in advance.

     

    AGM-84E incorrect cruise altitude.trk

  11. 6 hours ago, Northstar98 said:

    If a group is within ~3.5 nmi they work fine, though they do take a while to track a target.

     

    And you now don't have to use the trigger zones to get them to turn off, aircraft wondering into their engagement zone will automatically turn them on and they'll start looking in the approximate direction.

     

    I didn't notice much of a difference when pairing them up with a Kommandogerät 40 or the Freya but here are 3 mission files, all essentially identical, but testing whether or not having a fire-control director or a RADAR made any difference in late-dusk conditions.

     

    EDIT: You're on stable, while these are on the OB, it shouldn't make too much of a difference in terms of compatibility but this might explain the discrepancies.

     

    Thanks very much for the reply.  It definitely looks as though things have changed in the current OB, as the lights will not come on without triggers in stable.   Unfortunately your example missions don't work in stable but I suspect that when I get an update (hopefully soon), all things will work. 

     

    Thanks again for the work you did to assist me.

  12. Hi all,

    Thanks very much for the great instructions above. I'd like to be able to send a command to the rescue helo to RTB through a trigger, once we are all back on deck. I'm familiar with how to setup triggers but I'm having a lot of trouble working out the syntax for the script for the helo to RTB. Can anyone please help me out?

     

    Thanks in advance.

  13. What I'm seing is no spoilers come up with landing flaps retracted.

     

    Yes, that’s exactly what I’m seeing. I’m not sure when it was first introduced as I haven’t flown the F-14 for some time. Hopefully we will get acknowledgement by HB.

  14. Confirmed, something broke in the logic. Now with AUX flaps up and or maneuvering flaps down with the switch in BOTH or SPOILER BRK ONLY no spoilers come up with idle power. Only with AUX flaps deployed you get the full spoiler deflection. Definitely not how it should be or how it was before.

     

    Thanks very much for checking and confirming you are seeing the same. Can a Dev please note this in the bug tracker and fix when ready?

×
×
  • Create New...