Jump to content

falcon1823

Members
  • Posts

    21
  • Joined

  • Last visited

  • Days Won

    1

falcon1823 last won the day on July 1 2018

falcon1823 had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

falcon1823's Achievements

Newbie

Newbie (1/14)

8

Reputation

  1. @TheFlyGuy Get yourself over to the SimVRlabs club, join the club (so you can download the files without getting an error), and then get the LES saab SimVRlabs mod. Will fix all that right up. https://forum.thresholdx.net/topic/484-les-saab-340a/
  2. @boredtechie FIrst of all, you are absolutely correct. More serious issues and issues affecting the most users should be prioritized in my opinion as well (although, really, who are we to say what "should" be priority...i.e. maybe a huge, daunting issue is causing a bit of "head banging against the wall", and so - lets crank out something easy to make someone happy to get a little victory, then jump back into the more serious issue a bit more refreshed...) Anyway, using that report is bonkers. Here's why --> 11.20 was the first release of natively supported VR. It released on May the 7th. The usage data was as of June 4th, not even a month later. I don't know the numbers, but I don't give much stock in that report to try and estimate the numbers of VR.
  3. Hi awebneck, i might have some suggestions...but im a little unsure of what you are trying to accomplish. Your button works well executing the command, but youre looking for a dataref to do what now?
  4. Announcement: The SimVRlabs club at the threshold forums is now home. https://forum.thresholdx.net/clubs/12-simvrlabs/ The old website will be down for a while, maybe for good. Everything you could get from the old website is in the club as well as some new blog content that I put up yesterday for developers. What happened? I made a mistake when I renewed with GoDaddy, somehow I renewed the domain without also renewing the hosting. *facepalm* It lapsed and they want $149.99 to restore it with the content, else I can go with new hosting for cheaper but will have to rebuild the website from scratch. So...no. Executive decision. I can do more for you guys with that kind of money and time. Maybe in the future I can re-visit a website - I still own the domain for a long time. I invite you all if you haven't already to join the club over at Threshold for new files and content. I'm probably most active on discord, you can join the server at https://discord.gg/HJETTUb Also you can find us on facebook, I'm very active there as well. https://www.facebook.com/groups/494932957571552/ Thanks for understanding, and I'm in the weeds as much as ever trying to make our VR X-plane experience the best it can be. My wife can attest - she's the real rock star here. Thanks, Joe
  5. I got your request on the website and will totally help! Would be happy to. I will download the aircraft and take a look, and PM you @airfighter. Understand that there are 4 aircraft ahead of this one, (AOA osprey, AOA F35, Let L410, TBM900 cockpit update) so looking at a couple weeks out. Hopefully by mid December if you guys can stand-by a bit.
  6. I would head on over to their discord channel. https://discord.gg/7egEpuZ I find that is where support seems to be fastest and the devs see the support request more quickly.
  7. Yes, what you can click with the VR controllers you can also mouse-click outside of VR
  8. sim/radios/obs1_up and sim/radios/obs1_down sim/radios/obs2_up and sim/radios/obs2_down
  9. This has happened to me before when after takeoff I forget to disengage AutoCoursen and CTOT. The "150-160" range and gaining into a progressive overspeed porpoise is a tell-tale sign. Not saying this is what happened, but this is the first thing I would check on myself.
  10. LES Saab 340A VR Touch Controllers Mod View File This is a mod to fix a lot of manipulators that are otherwise unusable in VR with the touch controllers in the Leading Edge Simulations Saab 340A Version 1.5 for XP11. Manipulators that have been tweaked to work in VR are: Tweak Log: Rudimentary Pilot and Copilot teleport hotspots! (WIP) GPS Knobs, inner/outer Sun Shades, slide on rail and lower/raise All Light Intensity Rheostats Autopilot Altitude Selector Dial Com 1 and 2 Function Selector and Frequency knobs, inner and outer Nav 1 and 2 Function Selector and Frequency knobs, inner and outer ADF 2 and 2 Function Selector and Frequency knobs, inner and outer Transponder Function Selector and Frequency knobs CRS 1 dial CRS 2 dial HDG dial OBS Knobs IAS Bug knobs Altimeter baro pressure knobs Overhead DC Selector knob Flight Number Digit Wheels have been tuned for functionality Parking Brake orientation corrected (was previously reversed, now a push toward the floor pushes the knob down) Steering Tiller orientation corrected (was previously reversed, now a push toward the floor pushes the knob down) DCP Select knob tweaked Decision Height Knob rotation and push in/out tweaked (was previously reversed) And many, many other dials, knobs, and switches... These changes make the aircraft fully flyable using touch controllers in VR! With the exception the yoke. Known bugs or issues: - Some manipulators are a bit fiddly/touchy/sensitive, but at least they work correctly. **most fixed in 1.1 - CRS 1 knob seems to have two grab points, and one doesn't work. If you grab the CRS 1 and it doesn't turn, aim more for the base of the knob instead of the top of the knob. You can also grab the obs knob next to the CRT screen, it works beautifully. - Switches that should "snap" back to center, such as starter switch, bleeds, trims, V/S wheel, etc...they do not snap back to center using the VR controllers. I believe there is some custom "onmouserelease" gizmo code going on there, and the VR controllers aren't seen by gizmo as a "mouse". Fortunately the VR mouse works just fine, so I map the vr mouse to a button on my yoke and turn it on when I need to adjust trims. Everything else is still usable with the VR controllers. When you reset the bleeds it will stay in the reset position, but I've found that it's fine to leave it there. Same thing with the starter switch, it will just stay in the position of the engine you just started, but doesn't make a difference. If you want to snap it back to center, just use the VR mouse for now. I also map the vvi up and vvi down to buttons on my yoke so i don't have to use the V/S wheel when climbing/ascending using V/S mode. - Some custom mouse wheel code in 2d gets broken while using the VR mod, so if you are going to fly her in 2d you may want to revert back to the old .obj files. - gust lock only works using VR mouse. Again, I believe it's dependent on some custom gizmo mouse code. Disclaimer: This is not an officially supported LES update, so don't expect support from them on it. If you need help you can always ask me or just put your old .obj files back in your folders. If you lose the old files and just want to reset everything just reinstall the aircraft. Installation Instructions: Download the SaabVR-obj-v22.zip file (this is the latest version) Back up your LES_Saab_340_cockpit.obj from your Passenger Variant folder, your LES_Saab_340a_Cargo_cockpit.obj from your Cargo Variant folder, and your LES_Saab_340a_AEW_cockpit.obj from your Airborne Variant folder. Unzip the file, you'll find 3 folders, one for each Saab variant (passenger, cargo, airborne). Inside each folder you'll find a ***variant.txt file and a ***vrconfig file. Step 1: The ***vrconfig files just go in your Saab's corresponding aircraft variant folders. Easy. Step 2. You will need a text editor for this next part, I recommend notepad++ (free). The text inside these ***variant.txt files are intended to replace the current corresponding text in the obj files. Open the ***variant.txt file and copy all the text. Open the matching .obj file from you Saab's variant folder in your text editor. Search/find (or edit/find) for the world "TRIS". Highlight that line and all remaining text in the obj (shift click at the bottom of the file to do this quickly) and paste. Save the obj. (Not save-as, don't give it another name). Enjoy! **What's New in Version 2** This is a fairly major update. Along with the obj text modifications you'll now get vr_config.txt files to put in your aircraft variant folders as well. Changed a lot of axis manipulated knobs to their correct manipulation, getting rid of the "sliding up and down the colored line" effect. Also changed the sensitivity of countless dials and switches for a much better experience. Also added teleport hotspots to the pilot and copilot seat (sort of...it's a work in progress, but it works. The blue hotspot indicator that you're probably used to is currently a hoop about where the head of the pilot would be, but it works). All the manipulators that are still bound to color-line axis's can not be fixed because they are custom-code dependent (I think), and I've not found a way to fix them. They work as is, just have to deal with the axis slide. Submitter falcon1823 Submitted 04/08/2018 Category Plugins and Utilities
  11. Version 2.5

    27 downloads

    This is a mod to fix a lot of manipulators that are otherwise unusable in VR with the touch controllers in the Leading Edge Simulations Saab 340A Version 1.5 for XP11. Manipulators that have been tweaked to work in VR are: Tweak Log: Rudimentary Pilot and Copilot teleport hotspots! (WIP) GPS Knobs, inner/outer Sun Shades, slide on rail and lower/raise All Light Intensity Rheostats Autopilot Altitude Selector Dial Com 1 and 2 Function Selector and Frequency knobs, inner and outer Nav 1 and 2 Function Selector and Frequency knobs, inner and outer ADF 2 and 2 Function Selector and Frequency knobs, inner and outer Transponder Function Selector and Frequency knobs CRS 1 dial CRS 2 dial HDG dial OBS Knobs IAS Bug knobs Altimeter baro pressure knobs Overhead DC Selector knob Flight Number Digit Wheels have been tuned for functionality Parking Brake orientation corrected (was previously reversed, now a push toward the floor pushes the knob down) Steering Tiller orientation corrected (was previously reversed, now a push toward the floor pushes the knob down) DCP Select knob tweaked Decision Height Knob rotation and push in/out tweaked (was previously reversed) And many, many other dials, knobs, and switches... These changes make the aircraft fully flyable using touch controllers in VR! With the exception the yoke. Known bugs or issues: - Some manipulators are a bit fiddly/touchy/sensitive, but at least they work correctly. **most fixed in 1.1 - CRS 1 knob seems to have two grab points, and one doesn't work. If you grab the CRS 1 and it doesn't turn, aim more for the base of the knob instead of the top of the knob. You can also grab the obs knob next to the CRT screen, it works beautifully. - Switches that should "snap" back to center, such as starter switch, bleeds, trims, V/S wheel, etc...they do not snap back to center using the VR controllers. I believe there is some custom "onmouserelease" gizmo code going on there, and the VR controllers aren't seen by gizmo as a "mouse". Fortunately the VR mouse works just fine, so I map the vr mouse to a button on my yoke and turn it on when I need to adjust trims. Everything else is still usable with the VR controllers. When you reset the bleeds it will stay in the reset position, but I've found that it's fine to leave it there. Same thing with the starter switch, it will just stay in the position of the engine you just started, but doesn't make a difference. If you want to snap it back to center, just use the VR mouse for now. I also map the vvi up and vvi down to buttons on my yoke so i don't have to use the V/S wheel when climbing/ascending using V/S mode. - Some custom mouse wheel code in 2d gets broken while using the VR mod, so if you are going to fly her in 2d you may want to revert back to the old .obj files. - gust lock only works using VR mouse. Again, I believe it's dependent on some custom gizmo mouse code. Disclaimer: This is not an officially supported LES update, so don't expect support from them on it. If you need help you can always ask me or just put your old .obj files back in your folders. If you lose the old files and just want to reset everything just reinstall the aircraft. Installation Instructions: Download the SaabVR-obj-v22.zip file (this is the latest version) Back up your LES_Saab_340_cockpit.obj from your Passenger Variant folder, your LES_Saab_340a_Cargo_cockpit.obj from your Cargo Variant folder, and your LES_Saab_340a_AEW_cockpit.obj from your Airborne Variant folder. Unzip the file, you'll find 3 folders, one for each Saab variant (passenger, cargo, airborne). Inside each folder you'll find a ***variant.txt file and a ***vrconfig file. Step 1: The ***vrconfig files just go in your Saab's corresponding aircraft variant folders. Easy. Step 2. You will need a text editor for this next part, I recommend notepad++ (free). The text inside these ***variant.txt files are intended to replace the current corresponding text in the obj files. Open the ***variant.txt file and copy all the text. Open the matching .obj file from you Saab's variant folder in your text editor. Search/find (or edit/find) for the world "TRIS". Highlight that line and all remaining text in the obj (shift click at the bottom of the file to do this quickly) and paste. Save the obj. (Not save-as, don't give it another name). Enjoy! **What's New in Version 2** This is a fairly major update. Along with the obj text modifications you'll now get vr_config.txt files to put in your aircraft variant folders as well. Changed a lot of axis manipulated knobs to their correct manipulation, getting rid of the "sliding up and down the colored line" effect. Also changed the sensitivity of countless dials and switches for a much better experience. Also added teleport hotspots to the pilot and copilot seat (sort of...it's a work in progress, but it works. The blue hotspot indicator that you're probably used to is currently a hoop about where the head of the pilot would be, but it works). All the manipulators that are still bound to color-line axis's can not be fixed because they are custom-code dependent (I think), and I've not found a way to fix them. They work as is, just have to deal with the axis slide.
×
×
  • Create New...