Jump to content

RackMonkey

Members
  • Posts

    242
  • Joined

  • Last visited

Everything posted by RackMonkey

  1. I don't use any shaders, they cost to much in FPS with my setup. I do think your right about WMR and will dig around a little bit to see if I can figure it out.
  2. Yeah, clearing the environment data, FXO and metadata files in DCS is done on a regular basis and anytime I change drivers.
  3. All these drivers are WHQL so I assumed they would work without problems. I did a little testing with DCS. I put 22.6.1 back on and switched back to SteamVR. That got rid of the strobing but my FPS dropped to @35 on average and the display was fuzzier making seeing other acft or ground targets almost impossible. I went back to 22.5.1 and OpenXR and got my 45FPS back and can see acft about 30 miles out.
  4. I want to see if anybody else found this problem and what they did to fix it. This time I used DDU to clean out the old drivers and start fresh. The strobing seem to be a problem in VR, the WMR portal is the first VR software I open and it's strobing. The strobing continues in DCS and XPlane 11. I've tried everything that I know of to correct it and was hoping to get some other ideas.
  5. Checked some other servers and got mixed results. Since I mainly fly on the same server most of the time, I asked that they check to see if more than one boat is squawking the same TACAN. It's only MP servers and only seems to be on the SC's. It may be an ED bug. My testing was done under 2000ft and within 15DME. I crisscrossed the area to see if the HSI icon matched where the SC was and the course line was tracking in the right place. Once the icon froze I couldn't fly to the TACAN icon anymore.
  6. I just wanted to check that ED is aware that the TACAN does not work correctly on the SC. The TACAN is transmitting and DME seems to be correct but the course indicator locks up and jumps back and forth making it impossible to find the boat with it.
  7. Glad it's work well for you. I can't take credit though, I just pulled together tid bits from others work and organized it into a single file.
  8. @formaggioI'll contact you on Discord. Maybe together we can figure out how to do what you want. I tried to friend you this morning but it failed. You can try to friend me at Ares#9243. And what is "VA"? If I know what it is I might be able to figure it out. I also checked on the WH/BH. It's called "Boresight/polarity switch".
  9. To find out if I've left any performance on the table I've begun playing with other setting, and the first one I choose is motion reprojection. If it is on any other setting but OFF the display looks like I'm looking through a sheet of falling water. This seems to be a strange thing to do and completely different than when I had MR turned on in SteamVR. Does anybody know the what and why of this? On a side note, what is the difference of turning on MR in the OpenXR tools and turning it on in game with the toolkit companion?
  10. I think I read someplace that Norbert doesn't accept patrons. Is there a way to support him? Other than DEVRiM English cockpit mods VRNS is the most useful mod I have.
  11. With the popularity of OpenXR increasing and people jumping over from SteamVR do you think that Norbert will port his gem of a mod to work with OpenXR?? I've tried going back to SteamVR and the visual quality is just not as good as with OpenXR. While I really want to use VRNeckSafer I prefer to see the other guy when in a furball.
  12. It also has the zoom function available. I haven't seen the marker move on the MFD but the view does change.
  13. Nope, no GUI's. There's just to many changes we like to make to suit ourselves for ED to make GUI's for them all. I do wish ED would make things consistent among the acft so that it was easier to find where to make the changes though.
  14. Follow the folder path down to DSPL_Symbology.lua. In the thrid section down you will find the thickness and fuzziness setting. Play with those to find what you like in the HMD. Now, the color of your IHADSS (HMD) is currently default. I can't see that against the sky so I changed mine to a neon orange. If you want to change yours drill down to the materials.lua. Down at line 244 you'll find HMD. Under that is "HMD_GREEN". I don't know how to add neon orange to the materials files and have the HMD call it so I change the definition of HMD_GREEN to the RGB code for neon orange (255, 95, 31, 255). Because of it's title I'm pretty sure that only the HMD color will be changed to neon orange.
  15. This is what mine looks like with the MOD installed. There is no "Custom" before the MOD unless another MOD created it.
  16. I would have to say that TVV/FLIR is for an "either/or" switch where both positions are "ON". The zoom functions can go to any momentary switch, I.E. a hat switch OR if you only need medium and zoom function you can map them to any 2 position momentary switch that all HOTAS have.
  17. I looked at the file that Horus provided and it did everything that I was trying to do and more...THANK YOUR VERY MUCH Horus! In this zip is also a mod that thins the IHADSS symbiology to make it easier to sight the gun or just look around without your eyes being pulled to those FAT symbols. The root of the mod is DCS's mod folder. Let us know how it works for you and if you think there are any changes or additions that I might be able to do with my limited knowledge. AH-64D Single Pilot Mods.zip
  18. There seems to be 2 or 3 different ways to get this to work. I'll give them all a try today and create the file with the best of them. I'll post it here when I get it done. I am using the Quaggles/Wolfmuck software to add commands for my encoders so I'll see if I can get it working from that direction also.
  19. I did try it first in the installation folder on my D drive and when that didn't work I did try to but it in my SAVED GAMES folder. That didn't work either. I think I'll do like Needz and put it in the keyboard default.lua file and see if that works. I also tried putting it in a folder I use to modify the way my encoders work. It adds lines of code to make the encoders move faster. UPDATE Cut the line out of the "joystick" file and pasted them into the "keyboard" file. They are now showing up in DCS. I have to set them up and test them but it looks good so far. I think I'll try putting it into the 'saved games' folder so updates won't erase it all the time. If that doesn't work I'll make a package for OVGME that can be quickly enabled and disabled for updates.
  20. Well...now that mcfleck said it work's for him I'll revert back to the original default.lua with the following add to the bottom of the file. It should be the exact lines that Horus provided. Still nothing shows up in my controls to indicate a selection for the TAD settings.
  21. I do that a lot. In the most extreme cases it was to the left so I just chalked it up to retreating blade stall. I do get smaller dips to both the left and to the right and even the smallest correction seems to over correct it leaving me swinging back and forth under the blades. I am also seeing an almost complete loss of yaw authority at times and at other times it's so twitchy I can't keep the nose pointed in the right direction. After reading a lot of post concerning controllability I'm wondering if it might not be a difference in our input devices. Curves are not helping at all. I was hoping the last up date would at least dampen the problem if not fixing it completely but it doesn't seem to have done anything. ED may not have worked on it yet.
  22. I tried this this morning and couldn't get it to work. I matched your lines to that of the CPG file and found them all EXCEPT for your first line and I don't believe it has anything to do with the DOV line.. There were modifications of course. I copied the original CPG lines into the PLT default.lua to see if that would work, but it didn't. My PLT default.lua file now looks like this...can you tell what's wrong with it? ------------------------------------------------ -- CPG commands for the pilot ---------------------------------- ------------------------------------------------ {down = tedac_commands.LHG_TADS_SENSOR_SELECT_SW, up = tedac_commands.LHG_TADS_SENSOR_SELECT_SW, cockpit_device_id = devices.TEDAC, value_down = 0.0, value_up = 1.0, name = _('Custom_LHG TADS Sensor Select Switch - TV/FLIR'), category = {_('Custom')}}, {down = tedac_commands.LHG_TADS_SENSOR_SELECT_SW, cockpit_device_id = devices.TEDAC, value_down = 1.0, name = _('Custom_LHG TADS Sensor Select Switch - FLIR'), category = {_('Custom')}}, { down = tedac_commands.LHG_TADS_SENSOR_SELECT_SW_FLIR, cockpit_device_id = devices.TEDAC_INPUT, value_down = 1.0, name = _('LHG TADS Sensor Select Switch - FLIR'), category = {_('CUSTOM')}}, {down = tedac_commands.LHG_TADS_SENSOR_SELECT_SW, cockpit_device_id = devices.TEDAC, value_down = 0.0, name = _('Custom_LHG TADS Sensor Select Switch - TV'), category = {_('Custom')}}, { down = tedac_commands.LHG_TADS_SENSOR_SELECT_SW_TV, cockpit_device_id = devices.TEDAC_INPUT, value_down = 0.0, name = _('LHG TADS Sensor Select Switch - TV'), category = {_('CUSTOM')}}, {down = tedac_commands.LHG_TADS_FOV_SW_Z, up = tedac_commands.LHG_TADS_FOV_SW_Z, cockpit_device_id = devices.TEDAC, value_down = 1.0, value_up = 0.0, name = _('Custom_TADS FOV Switch - Z (Zoom)'), category = {_('Custom')}}, { down = tedac_commands.LHG_TADS_FOV_SW_Z, Up = tedac_commands.LHG_TADS_FOV_SW_Z, cockpit_device_id = devices.TEDAC_INPUT, value_down = 1.0, value_up = 0.0, name = _('LHG TADS FOV Switch - Z (Zoom)'), category = {_('CUSTOM')}}, {down = tedac_commands.LHG_TADS_FOV_SW_M, up = tedac_commands.LHG_TADS_FOV_SW_M, cockpit_device_id = devices.TEDAC, value_down = -1.0, value_up = 0.0, name = _('Custom_TADS FOV Switch - M (Medium)'), category = {_('Custom')}}, { down = tedac_commands.LHG_TADS_FOV_SW_M, up = tedac_commands.LHG_TADS_FOV_SW_M, cockpit_device_id = devices.TEDAC_INPUT, value_down = -1.0, value_up = 0.0, name = _('LHG TADS FOV Switch - M (Medium)'), category = {_('CUSTOM')}}, {down = tedac_commands.LHG_TADS_FOV_SW_N, up = tedac_commands.LHG_TADS_FOV_SW_N, cockpit_device_id = devices.TEDAC, value_down = -1.0, value_up = 0.0, name = _('Custom_TADS FOV Switch - N (Narrow)'), category = {_('Custom')}}, { down = tedac_commands.LHG_TADS_FOV_SW_N, up = tedac_commands.LHG_TADS_FOV_SW_N, cockpit_device_id = devices.TEDAC_INPUT, value_down = -1.0, value_up = 0.0, name = _('LHG TADS FOV Switch - N (Narrow)'), category = {_('CUSTOM')}}, {down = tedac_commands.LHG_TADS_FOV_SW_W, up = tedac_commands.LHG_TADS_FOV_SW_W, cockpit_device_id = devices.TEDAC, value_down = 1.0, value_up = 0.0, name = _('Custom_TADS FOV Switch - W (Wide)'), category = {_('Custom')}}, { down = tedac_commands.LHG_TADS_FOV_SW_W, up = tedac_commands.LHG_TADS_FOV_SW_W, cockpit_device_id = devices.TEDAC_INPUT, value_down = 1.0, value_up = 0.0, name = _('LHG TADS FOV Switch - W (Wide)'), category = {_('CUSTOM')}},
  23. I'm getting notifications that somebody has added to this topic, but I'm not seeing anything posted. So I can't respond to your post.
  24. I'd like to see it static, shrunk and moved to the side a little. It's not easy for me to concentrate, find, then refocus on the list of targets and separate them from the forward instrument panel.
  25. I don't have a problem moving around but in all the time I've had the Apache I've only been able to boresight the iHAADS ONCE. It's really a pain to try and fly with NVS when your seeing double images. I'm sure that part of the system needs some tweaking because I can't see a real pilot flying a combat mission like this.
×
×
  • Create New...