Jump to content

vortexringstate

Members
  • Posts

    96
  • Joined

  • Last visited

Everything posted by vortexringstate

  1. O.M.G I Missed the "USE MOUSE" check box in the VR tab. Dis regard the above post...! All is good in the world again. pheeew
  2. after the update to 2.5 Ob my onscreen mouse pointer wont move. I am using VR with Oculus Rift. I have tried in and out Full screen. I have to move my head then mouse click to select anything. The mouse does work as usual in an external view for panning around/zoom- its just moving the pointer in Menus and the blue cursor in game. sometimes I see the Menu selections flash when i wave the mouse around- like there is a ghost pointer 'behind' somewhere. Without the Rift (VR) - the mouse works fine. Grrrrrrrrrrr!
  3. yes. I got a this one to work: {down = device_commands.Button_16, up = device_commands.Button_16, cockpit_device_id = devices.ENGINE_SYSTEM, value_down = 1.0, value_up = 0.0, name = _('MW-50 Boost ON/OFF'), category = _('Engine Control')},
  4. 1.5.6 and yes- I reassigned the control binding after the changes.
  5. Hi again No.. The FW190 Armerment switch remains inverse. eg Weapons Armed when I switch down and Disarmed when I switch UP. Changing the values does not changed a thing?! I checked to see if i had my switch upside down - but No. Win Controller Properties shows the Switch closed when Up as expected. Wierd
  6. Unfortunately this Button 3 script works inverted also. Thanks for the reply LeCuvier
  7. Thanks. I suspected as much. Re Total Realism... My Sim chair/HOTAS/button boxes were designed to be a GENERIC controller for all my VR aircraft. I try to utilise as many common functions/switches as possible. I have only just started mapping the FW190 and have committed to the Undercarriage switch i have- which unfortunately dosnt use a Gear UP/DOWN push button. Thats OK- you cant win them all!. I have your 'how to' .pdf on control bindings but am still getting the occasional hiccup... Can you possibly help with these two? 1. My "Master Arm ON/OFF' script for the FW190 wont seem to work in the correct sense ie: Down for OFF and UP for ON. I have tried changing the values for UP and Down to 1, -1, 0, (every possible combination) but it always works in the wrong sense. The script below works correctly in other aircraft iv used it on. {down = device_commands.Button_13, up = device_commands.Button_13, cockpit_device_id = devices.WEAPON_SYSTEM, value_down = 1.0, value_up = -1.0, name = _('Master Arm ON/OFF Innes'), category = _('Weapon System')}, 2. FW190 Radiator Flaps. Im trying to have them operate from my HOTAS push Button (latchable) where they will open while i hold the button down/latch, and close when released. I managed to achieve this on the A10 but the FW190 uses "pressed" scripting which Im not familiar with. see below- my attempt is the last line: {pressed = device_commands.Button_14, cockpit_device_id = devices.CONTROL_SYSTEM, value_pressed = -0.1, name = _('Radiator Flaps Close'), category = _('Engine Control')}, {pressed = device_commands.Button_14, cockpit_device_id = devices.CONTROL_SYSTEM, value_pressed = 0.1, name = _('Radiator Flaps Open'), category = _('Engine Control')}, {down = device_commands.Button_14, up = device_commands.Button_14,cockpit_device_id = devices.CONTROL_SYSTEM, value_down = -0.1, value_up = 0.0, name = _('Radiator Flaps Toggle'), category = _('Engine Control')},
  8. New Question... Im trying to get the FW190 Landing gear retraction to operate from a single switch. ( the FW190 requires a GEAR RETRACTION SWITCH COVER to be opened before gear can be retracted) How can I bind BOTH the GEAR UP and the RETRACTION COVER OPEN to the same switch? eg, I want to select GEAR UP and it will open the cover AND select gear up.
  9. Ahhhh... that missing comma! Thats all it was! If it had been a missing washer, bolt, spring or pin, Id have spotted it right away- I guess im a mechanical guy... Got it working now... although i need to tweak it so it goes from OFF to ARM rather than OFF to SAFE. (I dont need the safe position) Thanks again.
  10. OK- so i stayed up mucking around with this much longer than i expected... I managed to get some Toggles to bind as I wanted (woohoo). eg Landing Light ON/OFF and Rear Doors Open/Close. I used Funkyfrankys code eg. {down = device_commands.Button_12, up = device_commands.Button_12, cockpit_device_id = devices.NAVLIGHT_SYSTEM, value_down = 0.0, value_up = 1.0, name = _('Landing Light ON/OFF Switch'), category = _('Ins Collective Stick')}, instead of the default: {down = device_commands.Button_12, cockpit_device_id = devices.NAVLIGHT_SYSTEM, value_down = 1.0, name = _('Landing Light Switch'), category = _('Ins Collective Stick')}, CrashO....Despite your EXCELLENT pictorial explanation, Im still trying to understand whats up with my setup. I simply can not find any Button 8 for the Armament system in my default.lua- despite it being coded exactly as yours in the clickable.lua??? Mine is Button 20 eg {down = device_commands.Button_20, cockpit_device_id = devices.WEAPON_SYS, value_down = 1.0, name = _('Armament Off/Safe/Armed Up'), category = _('Armament System')}, {down = device_commands.Button_20, cockpit_device_id = devices.WEAPON_SYS, value_down = -1.0, name = _('Armament Off/Safe/Armed Down'), category = _('Armament System')}, I cut and paste your supplied code straight into my default.lua but no joy. I tried changing the button to 20- no luck either. Ill be back tomorrow with more Questions. Thanks for the help guys.. keep it coming
  11. I chose an arbitrary toggle switch to experiment on as there are a bunch of toggles i want to bind to my button board- which has several 'Maintained ON/OFF' switches. It happened to be the "SAFE/ARMED Switcher" which you correctly point out, is in fact the Countermeasures ARM switch. (sorry for the confusion) Perhaps thats the issue- I will test on another Toggle- Tomorrow! Cheers
  12. its getting late here so i will take your HOW TO .pdf and read thoroughly and be back tomorrow.!
  13. Thanks for trying to help. Your code was cut and paste. similar effect as funkys- a flickering/intermittant result. Very frustrating as im sure iv read through this forum that this can work..?! Do i need to delete the original code im replacing- could that be 'corrupting' the added line? sigh.... i will go try with some other toggle functions and see if i can get it to work....
  14. Pleeeeease someone make a MD500 Scout/enforcer!
  15. Cheers Funky, I understand what you are saying now... but.... I tried that code you posted. It seems to work about 60% of the time... the rest of the time the Hueys Armament Switch 'flicks' and gets out of sync with the switch position. its like its only sensing a spike of current. however the Microsoft Controller button properties show the switch either ON or OFF (no flickering). I also tried it with several other switches with the same 'intermittent' effect. (ie its not a HARDWARE issue) Any ideas?
  16. Yes, You are correct- it dosnt work! but why does the same principle correctly work in the other example i give??
  17. This is driving me CRAZY! Iv read this entire thread and am still only having partial success... I have had success when creating a code for mapping a DCS Toggle switch (ie TF51 LANDING GEAR UP/DOWN ) to one of my On-OFF-ON switches eg. GEAR UP and Gear Down. eg Orig Code: {down = device_commands.Button_4, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 1.0, name = _('Landing Gear Up/Down'), category = _('Systems')}, My Code: {down = device_commands.Button_4, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 0.0, name = _('Landing Gear Up'), category = _('My Cockpit')}, {down = device_commands.Button_4, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 1.0, name = _('Landing Gear Down'), category = _('My Cockpit')}, But I CAN NOT get my ON-OFF type switches to take a DCS Toggle. ie UH1H SAFE/ARMED. Orig Code: {down = device_commands.Button_13, cockpit_device_id = devices.XM_130, value_down = 0.0, name = _('SAFE/ARMED Switcher'), category = _('Pedestal')}, My Code (which wont work): {down = device_commands.Button_13, cockpit_device_id = devices.XM_130, value_down = 1.0, name = _('SAFE/ARMED Switcher'), category = _('Pedestal')}, {down = device_commands.Button_13, cockpit_device_id = devices.XM_130, value_down = 0.0, name = _('SAFE/ARMED Switcher'), category = _('Pedestal')}, I still have to cycle the ON-OFF switch twice to get the Armerment switch to go ON-OFF Help needed please,,!
  18. That did it! The task bar must have been screwing things up! Thanks a bunch!
  19. Anyone got a solution to not being able to click "OK, CLOSE or FLY AGAIN" in the mission debriefing window while using Rift? My Vr settings are set to 'Use mouse'. I can click on everything in the startup menu but the briefing windows dont seem to work with the mouse clicks. Frustrating!
  20. Hi Andre. Just Ordered... ZFATESVPM Please make mine Black. Many Thanks!
  21. How I save my own Starting position. Ie I want to fly the UH1 from an 'outbase' each time but dont want to have to fly all the way there..
  22. Naieviety....? I have a new i7 CPU with GTX1060 and 1920x1080 monitor. Iv only played using Track IR on another PC prior to this build, so I am unsure what good/acceptable frame rates are to be expected in VR...? I thought the HUD overlay function was good to see Performance adjustments. Im not very conversant in the world of GFX settings: AWS, Super sampling, Pixel Density etc are things I have yet to fully understand esp in relation to each other for in game experience. I also bought the USB3 PCI expansion card which some are having difficulties with. I read somewhere the Tray Tool solved those issues (not that I was having issues yet). Is there known issues with the Tray Tool it or is it an un-necessary performance tax? Im finding it tiresome on the eyes tweaking all the variables to trying to benchmark what looks good vs perf! Should I simply be using FPS as a quantified way of tuning, or using the in game experience? I notice an uncomfortable 'shimmering' of light objects (such as building roofs) and power poles/towers. Id really like to tune this out/down. Any tips or performance tweaks would be greatly appreciated!
  23. Wooohoo. Got my PC and Rift up and Running. AWESOME experience and will always remember that buzz of being in VR for the first time! As someone else here has said..."Iv been waiting 25 years waiting for this !" Technology is making my dreams come true. Iv cleared up several of my questions and concerns now and am in the tweaking mode of getting the best out of the settings. trying to get Oculus Tray Tools to function properly but having trouble...
×
×
  • Create New...