Jump to content

Fubarbrickdust

Members
  • Posts

    167
  • Joined

  • Last visited

Everything posted by Fubarbrickdust

  1. I can personally guarantee that that the mod will leave you without any question as to wether a RIO pit button is active or not!! :thumbup: I know this because it was the hardest part to implement, and a personal milestone for the mod...took me quite some days to get right and looking clean! At the moment it's a dirty replace job for the vanilla files (packed OVGME ready mind you) so no 'Custom cockpit' option or IC pass I'm afraid. HB did an initial implementation for the option but, alas, it's broken and doesn't work...they have been informed/have acknowledged the issue but heaven knows how far down the list it is. All the tools and knowhow are in place to convert it to the relevant structure, however. So the day the option works from a HB/ED side I'll drop in the IC compliant version. Cheers, Brick.
  2. I made an interesting discovery while messing about with input default.lua files the other day... You can actually include the 'pressed' state with a line of code to combine all 3 input states into one binding. Works very well with momentary toggles and buttons, or standard toggles that are programmed to send a 'pulse'. And especially useful for in-game switches with covers, you can combine the entire cover and switch actions into one binding. A few examples from my own files: Mi-8 Fuel Shutoff Valve Switches & Covers {down=3009, pressed=3001, up=3009, cockpit_device_id=devices.FUELSYS_INTERFACE, value_down=1, value_pressed=1, value_up=0, name=_('Left Shutoff Valve Switch & Cover - OPEN ► ON ► CLOSE'), category=_('[11] Centre Overhead Panel - Fuel System')}, {down=3009, pressed=3001, up=3009, cockpit_device_id=devices.FUELSYS_INTERFACE, value_down=1, value_pressed=0, value_up=0, name=_('Left Shutoff Valve Switch & Cover - OPEN ► OFF ► CLOSE'), category=_('[11] Centre Overhead Panel - Fuel System')}, {down=3010, pressed=3002, up=3010, cockpit_device_id=devices.FUELSYS_INTERFACE, value_down=1, value_pressed=1, value_up=0, name=_('Right Shutoff Valve Switch & Cover - OPEN ► ON ► CLOSE'), category=_('[11] Centre Overhead Panel - Fuel System')}, {down=3010, pressed=3002, up=3010, cockpit_device_id=devices.FUELSYS_INTERFACE, value_down=1, value_pressed=0, value_up=0, name=_('Right Shutoff Valve Switch & Cover - OPEN ► OFF ► CLOSE'), category=_('[11] Centre Overhead Panel - Fuel System')}, You can also combine down & pressed on their own and flick 2 switches simultaneously... Mi-8 Batteries 1 & 2 {down=device_commands.Button_3,pressed=device_commands.Button_2,cockpit_device_id=devices.ELEC_INTERFACE,value_down=1,value_pressed=1, name=_('Battery 1+2 Switches - ON'), category=_('[06] Right Side Panel')}, {down=device_commands.Button_3,pressed=device_commands.Button_2,cockpit_device_id=devices.ELEC_INTERFACE,value_down=0,value_pressed=0, name=_('Battery 1+2 Switches - OFF'), category=_('[06] Right Side Panel')}, This ability opens up an extra level of flexibility that I was previously unaware of. And can be used quite creatively to to better utilize button and switch real-estate. F/A-18C Parking Brake, twist & Pull in one pulsed action {down=gear_commands.EmergParkHandleSelectPark,pressed=gear_commands.EmergParkHandleOnOff,up=gear_commands.EmergParkHandleSelectPark,cockpit_device_id=devices.GEAR_INTERFACE,value_down=1.0,value_pressed=-1.0,value_up=0.0,name=_('Emergency/Parking Brake Handle [3 Action Special] - CCW+Pull'),category=_('[13] Front Left - Vertical Panel')}, I hope some of you find this useful. Cheers, Brick.
  3. For those that are experiencing the bad tracking stutter with 1.38 - you might wanna check this out n give it a go. I mananaged to completely resolve my issue. Might work for some of you, hopefully so. Seems there might be an issue with the new update not liking ASMedia USB 3.1 gen2 ports. Check the post and reddit link within. https://forums.eagle.ru/showpost.php?p=3953300&postcount=8 Cheers, Brick.
  4. +1 Just received the forced update to 1.38 - totally f*@ked my tracking! Same issue as reported by others who are affected - micro-freeze/stutter when moving head about. That's me out unless I can find a way to hack 1.37 back in or it gets ironed out by Oculus. EDIT: I seem to have fixed it!! - DL'd & ran the Oculus installer, ran the repair function which re-installed all the Rift gubbins (still 1.38, no firmware reverts). - On a whim I 'removed the device' in the software & re-ran the HMD setup, however, I used a different USB port/controller on my MB (I believe it was plugged into a USB 3.1 gen2 port. Now standard 3.0)... Low & behold, fired everything up expecting no change whatsoever - Wrong! Tracking was back to being smooth as silk! I'm not quite sure which particular part of the process fixed the issue, but in this particular instance, on my machine, something squashed the gremlin! I'm not saying this is a staunch fix for everyone...but might be worth a shot if you've not tried it so far. EDIT 2: Also found this: https://www.reddit.com/r/oculus/comments/c1wd9y/possible_fix_for_138_rift_s_stutter_problem/?utm_source=share&utm_medium=ios_app Which would also tie into the above as I believe the USB 3.1 gen2 port I was using is indeed on an ASMedia controller. Cheers, Brick.
  5. Just thought I'd pop this here... Nothing too fancy or complicated, bit of an experiment n very simple restyle for one of my favorites, the MiG-28. No tweaks or major changes to anything. Cockpit trim in black, that's all. Just the thing for when you got a grinning douche-bag & his back seat groupie trying to snap Polaroids of your ride... IC compliant too, so that's nice. LINK: DCS: F-5E - Brickdust's "Foreign Relations" Dark Cockpit Any issues just give a shout and I'll take a look. Enjoy, Brick.
  6. Time for me to eat a bit of humble pie and apologize to any devs that may have investigated based on my previous post... Found the problem - I hadn't disabled 2 little mods made for the F-5E...that for quite some time had worked happily without issue through multiple game updates. Not trying to excuse, just mentioning. One that fixes the RWR search function, and another that hacked in NVG support. Both caused a crash on the comms menu. Anyone else experiencing the same, double check your F-5E mods, if using any at all. Brick. EDIT: Disregard all of the above. Crashes still persisted. Disabled all mods, still crashed. Did a clean & repair...All good. Re-enabled all mods. All good. Apologies, I'll shut up on the whole subject now.
  7. +1 Can confirm. happened to me 3 times today with instant CTD. 1 in SP, requesting rearming from a hot start. 2 in MP from cold when contacting Ground Crew for power. I did not try to test any more variables as it seems quite consistent - Something is rather broken with the F-5E and the comms menu at the moment.
  8. Noticed this just now - Not the biggest thing in the world but quite nice for when those trigger lists start to get beefy: Nice :thumbup:
  9. I've had this too, agreed it's quite bothersome. The trick I found was configure the carrier group so the support ships will be on the outside of the carrier turn radius. Not ideal, but stops this behaviour/bug.
  10. Mod Updated to v0.5 Hey all, Thought I'd best do a little update as it's been a while - I was gonna wait until the whole thing was complete, but as the going's been a little slow of late I'll throw up what has been worked on. See 1st post for link: HERE Changelog: v0.5 - More RIO Pit...but not all. RIO annunciator and warning lights complete. Additional RIO panels reworked - RWR, ECM, CMS, Lights & COMM/NAV CMD. A few roughmet errors fixed. Cheers & thanks for all the kind shouts and encouragement :thumbup: Brick.
  11. You are very welcome good sir. Glad it's helping out :thumbup: Heya reaper, Irritatingly, work and real life has drastically reduced my free time recently. What little DCS time I've had I've chosen to do a bit of flying and venturing into MP as well as enjoying the Rift S. That's not to say the project's abandoned, far from it...it's quite near to being done, just a few more panels on the back seat to go. Out of curiosity, are you using the most recent version (0.4)? Reason being that the bulk and business end of the RIO pit is in that release, I'd say about 75% of the panels. Check it out if you haven't, it may well tide you through. Cheers, Brick.
  12. Good man :thumbup: I was digging around in the commandmenu.lua but only found tweaks for the menu width and font size. Thanks for sharing. I feel another mod making it's way to OvGME. Hopefully ED will fix the issue before too long.
  13. As per the title. After the latest open beta update (2.5.5) the lower sections of a fully populated radio menu gets cutoff and truncated in VR. This happens regardless of the new font size setting used - Even at 1x the lower entries get cutoff, the issue gets worse the higher size setting used. Seems like the viewport 'box' size allocated to the radio menu isn't extending low enough or towards the right enough, and doesn't account for any text entries that are longer and may extend further than that of the top layer radio menu. To test: Open up any layer that may be well populated with entries that are more than one word (eg, ATC sub menu with more than 6/7 airfields available). Using Rift S if it makes any difference. Cheers, Brick.
  14. I can concur and verify - I've bought several 'mechanic' pieces for my builds from GVL224 over the years: The business end of my DIY Throttle and Mech panel (landing gear lever) are using his lever modules. Quality is high. Prices are very reasonable. Communication is good. Order fabrication time and shipping is also very good. Brick.
  15. As a fellow pit/DIY controller builder, I understand your position. All is not lost however as pretty much any knob (or switch for that matter) can be assigned to an axis. See post for example: https://forums.eagle.ru/showpost.php?p=3852380&postcount=72 You can also study the attached file to see what I'm referencing in the post. But i'm afraid, yes, you will need to become very familiar with several specific lua files in DCS in order to get the most flexibility with a home cockpit. Namely clickabledata.lua, devices.lua and default.lua for any given module. The bulk of editing will be done in the default.lua file. Here's a handy thread to get you started: https://forums.eagle.ru/showthread.php?t=89226 Cheers and happy digging, Brick.
  16. I use a pair of M30’s - it’s snug. But they fit.
  17. Heya nrosko, I know the question was not pointed directly at me, but I can answer as I've come directly from a CV1 to Rift S: Mura? - Completely gone. Non-existent now. Colour banding? - Practically eliminated in comparison to CV!. I really had to go looking for it, and even then it was very mild at best. Godrays? - Massively reduced. Which has a very positive impact on night flying in my opinion. Of course these observations are exactly that, my subjective opinions moving from my CV1 to Rift S, but they are heavily based on some clear and undeniable objective facts. Hope it helps, Brick.
  18. This is a really curious discussion, as my experience with night flying and Rift S (vs CV1) has seen a vast and significant improvement! To the point where I quite enjoy night flights now, as opposed to not at all. From my perspective (and subjective opinion) there has been one negative trade off to give several really positive ones: Negative: - Black levels. No more ink black. But the levels you do get are quite useable. Positive: - Zero mura or grainy effect that follows your gaze. - vastly reduced god rays, so no massive unrealistic light spill from sources. - significantly reduced colour banding throughout. Especially noticeable during dusk/dawn.This I didn’t expect, but am really happy about as before the banding was ridiculous! Before the Rift S I really wanted to enjoy and utilise flying at night. Because of the amalgamated issues I found the experience quite poor. Now, although not perfect, I find the experience quite useable and even enjoyable. I plan to explore it a lot more...I did my 1st IFR Lansing in the AV-8 using just the AWLS the other day and it was a blast! Brick.
  19. Two ideas/wishes in one really - Not mutually exlusive. 1. It would be quite nice to have a functional iteration of the F10 map (zoom & move, etc.) from within the current kneeboard. And to follw, for those of us that enjoy the challenge of NDB/Radio navigation and 'old school' navigation... 2. the inclusion of a few extra 'map & pencil' tools to aid in navigation, expanding on the functionality of the current ruler tool, eg: ability to draw more than one line with distance and bearing for intersecting different radio signals, a 360deg protractor ruler, virtual pencil compass, etc... Just a thought that it'd be a cool feature for use with modules without moving maps, etc. Brick.
  20. You weren't joking were you, Wags! It was your OP on this thread that sold me into a no questions pre-order. Prior to that I was somewhat sceptical regarding the S.
  21. Cheers, Jav Fact is, after I've tied up the loose ends and push the final release I'm now struggling to choose which pit is next for a makeover...because thanks to the Rift S, I'm not sure cockpit legibility is gonna be an issue moving forward! Which is a great place to be for all of us VR heads! :pilotfly: Brick.
  22. I believe this is the mod you are looking for: https://forums.eagle.ru/showthread.php?t=238208 :music_whistling:
  23. I have a rig with a NLR V3...not quite as extreme as some of the bigger setups, but should be enough of a test to give a good idea. I’ll chime in with feedback once I get it all up n running.
×
×
  • Create New...