Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by Vladinsky

  1. I saw a significant VR performance increase going from my 4690K(4.2GHz) to a 10600K, not so much in terms of maximum framerate but reduced stuttering and increased lows.

    Unfortunately no frametime numbers due to the OTT overlay not working.


    However, the YAAB: Yet Another Arma Benchmark saw an 85% performance increase.


    This is with a 2080Super, 3600MHz CL16 and after overclocking, 4.9GHz all core/4.8GHz cache.

  2. As a module in DCS without multicrew I imagine you would just cram everything you need onto your joystick/collective regardless of where it's actually located in the cockpit.




    My transducer requires about 2lbs for maximum input, which is about the same force required to actuate the trim switch on the Lynx cyclic I use as a joystick, I think it would work ok.



    As for why they did it, literally no idea. But if I were to speculate, perhaps the collective was too crowded with switches already, or perhaps it made more sense to disconnect the copilot stick rather than installing a separate sensor control grip due to space restrictions.



    Those military grade buttons, too costly or impossible to source for a grip, from say Microhelis or Komodo? I have no idea how these last ones feel like, but it would be nice to have an option like that, for a higher price.



    You can get them but they'll be very costly if you're buying them new from lets say, OTTO. You can however find good deals on ebay from time to time, search for otto pushbutton or otto switch. Typically the sellers are located in north america so you might get hit with import tax too.

  3. Going from a 4 way switch to a force transducer for sensor control is the joystick equivalent of going from a monitor to VR, that's how big the difference is. It's specially noticeable in the Ka50, zero curves or saturation required.


    As for having it on the cyclic, that's only an issue if there's very little resistance/no force trim system. The OH-58D takes it a step further and gives you the option to disengage the copilot cyclic from the control system. The copilot cyclic is also the only one with a transducer.

    Its location instead holds the force trim release switch on the pilot side.

  4. I'm having some difficulty as well. I'm sure it's operator error, but I've not yet determined what part I'm doing wrong.


    Target is located around Sochi. Follow Wags' video on using the C version.


    What seems to be happening is that the JSOW is going a few meters beyond the target. I noticed on the waypoint can only go down to about 98 feet. This makes me think the JSOW thinks the ground is at 98.



    It's trying to fly through the point in space defined by the waypoint, since the lowest you can place waypoints is 98 feet AGL that puts the waypoint elevation at ~177 feet, and as such it will fly through the point 98 feet above the target, exactly as it has been instructed.

    If you edit the waypoint to correspond to the ground, 79 feet in this case, it hits dead on.





  5. No problem, you can disable exported displays in the cockpit by commenting out "render_purpose.GENERAL," on line 81 in "Scripts\Aircrafts\_Common\Cockpit\ViewportHandling.lua". This will fail integrity check though.



    You should be able to find the name of the viewport for any module by going to the module folder\Cockpit\device name\init file.

    In some like the F18 they're in DCS World\Mods\aircraft\FA-18C\Cockpit\Scripts.

    You can even add it if it's not natively exportable.


    For example if I wanted to export the mirage RWR I would go to "DCS World\Mods\aircraft\M-2000C\Cockpit\RWR\RWR_init.lua.

    Check if the


    line is present, if it isn't, add it.

    Then add the line


    It doesn't seem to matter where exactly you put them.

    I'm not sure how to add new ones for FC3 aircraft but they should output the F15 radar display to the LEFT_MFCD and the flanker/mig 29 HDD to the RIGHT_MFCD by default.

  6. The F18 being blurry is a bug that seemingly appears when your game vertical resolution is above 1080p.


    For the harrier you'll have to use the "Left/Right MFCD Export View ON/OFF" keybinds.



    As for the rest, a simple way to set it up would be aligning your monitors as such in windows.





    From there set up the lua in a fashion similar to this. The cockpit is showing up behind them because you've put the MFCDs under the Viewports category.



    It should be as simple as setting your in game resolution to your monitor width plus the two other displays x 1440 and play around with the X/Y positions until you've got the exports right where you want them.

    The code below should in theory position each export window at the top left corner of each display.





    _  = function(p) return p; end;
    name = _('HadiMFDs');
    Description = 'Main Screen and L-R MFDs'
    Viewports =
      Center =
             x = 0;
             y = 0;
             width = 3440;
             height = 1440;
             viewDx = 0;
             viewDy = 0;
             aspect = 3400 / 1440;
       x = 3440;
       y = 0;
       width = 570;
       height = 570;
       x = --Center viewport width plus left MFCD display width;
       y = 0;
       width = 570;
       height = 570;
    UIMainView = Viewports.Center

  7. If anyone is still struggling to visualize the force trim here it is in action.




    This Mi24 is equipped with more advanced trim actuators offering both trim release and a trim hat like what you'd find in a plane.


    Mind the volume.




    And a fantastic home made version.



    But on the topic, I used a warthog with a 10cm extension for about 3 years and I found it worked very well. If you only intend to fly helicopters I'd highly recommend removing the main spring, it makes flying much more intuitive in combination with the "Joystick Without Springs and FFB" trimmer mode.


    The drawback is that you'll most likely not be able to let go of the stick but I consider it well worth it over doing the recenter dance every time I trim.


    Just be careful if you decide to go that route, Thrustmaster wires tend to be rather fragile(as I discovered the annoying way).


    "It's very much against the design principle we've had when developing the aircraft where whatever is in the backseat is handled by the backseater (be it JESTER or a human RIO) and we will make sure that "purity" is kept as much as we can.

    That said, we realize that launching sans Jester operating the TGP is a bit of a pain right now, especially in MP - so we're not doing anything on this until we get Jester to learn the LANTIRN, which shouldn't be long. :)"

  9. TL;DR That GBU-12 should never be dropped. It has to stay there.


    Where does this idea come from? The TPOD is below the asymmetric limits of vertical take off, landing and shipboard STO on stations 3 and 5. Additionally it's also below the limits for STO/CTO on stations 2,3,5,6.


    The only case you could make for using a bomb as a counterweight would be for a shipboard STO on stations 2 and 6. The pictured configuration can take off and land anywhere unrestricted with or without the bomb.

  10. "When the gear is retracted, a hydraulic actuator adds additional centering forces at airspeeds higher than M0.8 and rudder pedal displacements of more than 24 mm, equivalent to 6 degrees of rudder deflection."


    "It is strongly recommended not to override the artificial stop"


    It is stated that the rudders deflect 25 degrees to either side so rudder inputs above ~25% of travel to either side should be avoided in flight and definitely above 485KIAS when they implement vertical stab overstressing, assuming that isn't in yet.

  11. I probably didn't set my Mode 4 correctly, there was indeed an element of sarcasm included.


    I am very interested in finding out exactly what would warrant an entirely new module though when the department of the navy literally states that it's the same aircraft with a radar fitted and integrated.

    I'd certainly hope they're competent enough to know what they're flying.

  12. No? What other avionics changes were there besides addition of a hornets an/apg65 radar and ability to fire Ammrams?


    They are in fact so fundamentally different that they use the exact same flight and tactical manuals, checklists and performance charts as the night attack.


    "The AV-8B radar aircraft is the same as the AV-8B night attack with the APG-65 radar incorporated. The addition of the APG-65 radar enhances mission effectiveness through improved navigation, air-to-surface, and air-to-air weapon systems capabilities." - A1-AV8BB-NFM-000-2011

  13. The TDC Slew Horizontal (mouse) and TDC Slew Vertical (mouse) are part of the default mouse keybinds located in Config\Input\Aircrafts\Default\mouse\default.lua

    It is loaded by virtually every module because the same file also controls the mouse camera axis.


    As far as I can tell it does nothing for most of them, each module with a slew input is going to have its own defined through the module specific joystick and keyboard default.lua, which is why you usually see duplicate binds.


    In the FA-18 the proper binds are called "Throttle Designator Controller - Vertical Axis" and "Throttle Designator Controller - Horizontal Axis" instead.

  14. Valid for the ARBS/LST. The aircraft has no idea which code any of the bombs are set to, you change it with a screwdriver on the ground and that's that, the only thing we get to do is pick wether the arming wires are held on release.



    I'm assuming the bombs are still magically changing code in the air then? Haven't flown the Harrier in a while.

    If they are I'd expect it to move to the kneeboard instead(with the correct range) as the module matures.




    E: I've just had a look at the GBU 12 in the F5 kneeboard and they do have the correct code limitations.

    The Mirage on the other hand lets you pick anything between 1111 and 1888. Potentially worth reporting.

  • Create New...