Jump to content

Mordants

Members
  • Posts

    190
  • Joined

  • Last visited

Posts posted by Mordants

  1. DCS 2.9.4.53549

    The latest update (before the hotfix) includes the item below, but where in the menus is it? I looked in my control settings and was unable to change a joystick name.

    GUI. When the user edit the joystick name and pressing <ENTER> (as suggested by tooltip), OPTIONS window closes - fixed.

  2. DCS 2.9.4.53549

    The latest update (before the hotfix) includes the item below, but where in the menus is it? I looked in my control settings and was unable to change a joystick name.

    GUI. When the user edit the joystick name and pressing <ENTER> (as suggested by tooltip), OPTIONS window closes - fixed.

  3. 24 minutes ago, YoYo said:

    I have v62 still, I did nothing but Today this pop up appeared 🤪 :

    lPiS3vl.jpg

    This is the last week of March so parhaps we will see the patch soon, I hope.

    Me too, so I've snoozed.
    But what does it mean below when Lange888 says create a new file with no extension I've done the folder bit but what type of "File" with no extension?


     

    Simply browse to C:\Program Files\Oculus (or where you installed your application)
    Rename folder \Staging to bak.Staging
    Rename folder \tmp to bak.tmp
    Create a new file called Staging (with no extension)
    Create a new file called tmp (also, no extension)
  4. 1 hour ago, JohnW71 said:

    I have it under a different path but its here anyway. Weird how this isn't working as it was, it used to be so easy.

    default.lua 189.97 kB · 0 downloads

    I got the keybinds from here originally https://github.com/Munkwolf/dcs-community-keybinds, though I only used a few bits not the whole mod. Anyway it might have been updated since so maybe worth checking this mod out.

    What path did you get it from, maybe I'm getting it wrong?

     

  5. 15 minutes ago, JohnW71 said:

    Sure, here it is

    Thanks you really are a star. Your clickable.lua file is the same as mine so I don't understand why you have the keybind data and I dont. Maybe, and this will be my last shot you could attach your keyboard file located at Saved Games\DCS.openbeta\InputCommands\Mi-24P\Input\Mi_24P_pilot\keyboard. Then at least I have tried all variables, Thanks.

  6. 12 hours ago, JohnW71 said:

    This still has not worked for me, however the attached clickable data does not show the controls either. Can I be a pain and see if yours is similar? Or attach yours and I can compare.

    This file can be found: DCS World OpenBeta\Mods\aircraft\Mi-24P\Cockpit\Scripts      clickabledata.lua

    Thanks again for your help.

    clickabledata.lua

  7. 6 hours ago, JohnW71 said:

    I had a quick look in DCS earlier (with no controls attached) and couldn't find them in the bindings either, should be under Instrument Panel but not there. Now I have my controls plugged in, go into DCS and there they are as expected. I have no idea why they wouldn't show before, maybe recent patch/bindings changes has muddled something here. 

    Out of some old habit I have always placed my custom bindings in the file just before the '-- Clock' section. Anyway good luck, hope this helps somehow.

    image.png

     

    Could you attach your Joystick lua file, and I'll give it ago. Definately weird though.

     

  8. 1 hour ago, JohnW71 said:

    It's not there yet, I paste this into the file \DCS World OpenBeta\Mods\aircraft\Mi-24P\Input\Mi_24P_pilot\joystick\default.lua to add these bindings:-

            -- RALT
            {cockpit_device_id = devices.RADAR_ALTIMETER, pressed = ralt_commands.ROTARY, value_pressed = 0.025, name = _('Radar altimeter - Down (Slow)'), category = {_('Instrument Panel'), _('Custom')}},
            {cockpit_device_id = devices.RADAR_ALTIMETER, pressed = ralt_commands.ROTARY, value_pressed = -0.025, name = _('Radar altimeter - Up (Slow)'), category = {_('Instrument Panel'), _('Custom')}},
            {cockpit_device_id = devices.RADAR_ALTIMETER, pressed = ralt_commands.ROTARY, value_pressed = 0.05, name = _('Radar altimeter - Down'), category = {_('Instrument Panel'), _('Custom')}},
            {cockpit_device_id = devices.RADAR_ALTIMETER, pressed = ralt_commands.ROTARY, value_pressed = -0.05, name = _('Radar altimeter - Up'), category = {_('Instrument Panel'), _('Custom')}},
            {cockpit_device_id = devices.RADAR_ALTIMETER, pressed = ralt_commands.ROTARY, value_pressed = 0.1, name = _('Radar altimeter - Down (Fast)'), category = {_('Instrument Panel'), _('Custom')}},
            {cockpit_device_id = devices.RADAR_ALTIMETER, pressed = ralt_commands.ROTARY, value_pressed = -0.1, name = _('Radar altimeter - Up (Fast)'), category = {_('Instrument Panel'), _('Custom')}},

    Thanks, but I have found that I have these lines already. So not sure what I need to incorperate this into the key bindings.

  9. 15 hours ago, Jimbo357Mag said:

    Well are useing rudder pedals but as long as the weels are locked I have no issues in useing a normal gaming chair. But as soon as they are not a propel my self right in to the Book rack behind me 🙂

    The thing is I noticed both chairs you pointed out didn't have locking wheels.

  10. As someone who has a Secretlab chair who changed to locking castors, I would think about either locking castors or someway of anchoring yourself when oprating the rudder pedals if you have them. Caught me out!

     

    • Like 1
  11. 5 minutes ago, AhSoul said:

    I'm wondering about the 4080 Super about to come out. It's like 1/2 the price of the 4090 and I guess can't be thaaaaaat far off in terms of power?

    Difference I believe is the 24gigs of VRAM

     

  12. 16 minutes ago, AhSoul said:

    I've done most of that (I think I still have the clouds on 'standard') - pretty much changing one at a time to see what makes a difference.

    Kinda feels like I've gone as low in terms of detail as I want to get - I don't want to play in VR if it looks <profanity> I guess 😄

    Maybe hardware is the only solution - just not sure which thing to change first.

    Feels like there's so many variables though....

    Very useful!

    Just thought, I don't have vsync on - it's still off from when I was playing on my Gsync monitor. Should I turn it back on again for VR?

     

    Just to add that I never looked back once I got a 4090 last year for my system. The lastest DCS update fixed the freezes and stutering for me.

  13. 1 hour ago, Ghostmaker said:

    Before i go on dcs to do this. Is there a pilot / co pilot for the herc? Right shift P doesnt work for this aircraft however ive just seen this on the discord?

    Screen_210524_214340.png

    Never seen it before.  Doesn't affect my game play at all.

     

  14. 3 hours ago, Ghostmaker said:

    When you download the textures on the first post where do you save these? I created a fokder "Liveries" within mod folder and extracted into there but i cant change it in game or see the different textures. What am i doing wrong here? Just flew the herc that was great fun

    Hi mine are here

    Saved Games/DCS.openbeta/Mods/aircraft/Hercules ver 6.8.2/Liveries/Hercules

     

    Hercules Liveries.png

    • Like 2
  15. 23 hours ago, Ghostmaker said:

    Cheers mate, sorry been a late reply. Once downloaded this file how do i get it to work in Dcs 2.9 open beta? Im new to all this pc stuff 😅😁👍🏻

    Unzip file and put the folder into saved games/DCSopenbeta/Mods/aircraft and away you go. Do not put the folder in the DCS World root folder.

    • Like 1
  16. 1 hour ago, Willoughby888 said:

    I've been using XRNS without issues for a while but, since 2.9 when I turn to look back my head moves sideways (opposite to the way I'm turning my head) so that I'm looking backward but at the back of my seat. initially this was just odd occasions, now it happens every startup. I've tried DCS file repair, starting XRNS before and after starting DCS, deleted and reinstalled XRNS and checked that everything is updated.

    I'm using quest Pro with standalone DCS MT.

    Any advice would be greatly appreciated.

    I had similar shenanigans too, my solution was to zero out the translations and shift an extra degree into rotations. Whether or not it had anything to do with it, the next time I used it, it was fine.

     

×
×
  • Create New...