Jump to content

severniae

Members
 View Profile  See their activity

  • Posts

    60

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Posts posted by severniae

  6. [OPEN] CTD on start in VR, also with V1.1.0

    in Crash To Desktop

    Posted

    2 hours ago, Sleepy81 said:

    Thanks for the pointers. I run no SS and no SSAA, so basically the default full resolution of the 8kx is being rendered. I have also tried to run the sim with every setting sett to minimum or off, and it still CTDs when entering VR the second time. So it seems strange that it should then eat up 12GB if VRAM. But maybe x-plane does not “release” the VRAM correctly when exiting VR, and it just filles up on the next entry into VR? 
     

    Anyways, it’s working fine now. Nice 30+fps even with ortho and Global Traffic, so I’m happy that at least there is a walk around that works for me now. 

    Try disabling VR, then close down and restart steam VR.

    Yes I suspect there is a memory leak or similar when entering/exiting VR. I really hope it has received some attention in XP12.

    • Like 1

  8. [OPEN] CTD on start in VR, also with V1.1.0

    in Crash To Desktop

    Posted

    52 minutes ago, Sleepy81 said:

    I figured it out! :)

    So, Apparently there is an x-plane bug that affects me. I cannot re-enter VR in X-plane after having been in VR during the same session. So, If I go from 3D -> 2D ->3D , then I get a CTD 100% of the time, regardless of which aircraft I use, or when I enter VR the second time. So, I've been starting up X-plane in VR from the get go, as this has worked on all other aircraft, and just stayed in VR the entire time. With the CL650, I tried to start using 2D mode, but for whatever reason it always tries to start X-plane in VR mode (initializing VR) on the first load screen, even when selecting 2d mode from the Steam Launch options. Even if my googles where powered off, and it failed to enter VR, and defaulted to 2d, it apparently "burned" my one shot of getting into VR for that session. So when I tried to enter VR after having entered the CL650 cockpit, it CTDed. 

    So, then I figured I hade to double check everything, and really make sure x-plane did not try and initialize VR until I was in the cockpit.

    So, this is what I did:

    1. Enter X-plane, ensure VR is off in the settings. 

    2. Quit Xplane.

    3. Quit Steam just to make sure that any part of SteamVR services are not "lingering" in the system.

    4. Start X-plane from the .exe file

    5. X-plane now starts in 2d mode, and does not try and initialize VR.

    6. Get in the CL650 cockpit in 2d mode.

    7. Enable VR mode from the settings menu, and presto, CL650 in glorious 3d VR! :D

    Thanks to all that have helped, and hopefully this post might help others who might have the same issue! 

     

    Now, I just need to remember to turn off VR mode in X-plane settings each time I quit to avoid having to do points 1. and 2. above every time I want to fly the CL650. :)  And I hope HotStart can make the entire experience compatible with VR, (FBO/Career/Non-persistent selection menu etc. etc.) compatible with VR so I can stay in VR from the start, and never needing to be in 2d mode. :)

     

    Glad to hear you have it working. A few points:

    The reason xplane crashes with switching between 2d and VR is due to it running out of VRAM and crashing. The 8KX has a monstrous resolution so if you have any kind of super sampling at all, on a 3080 you will burn through VRAM in no time. I have a 3090 and even that can hardly handle the 8KX.. It'll be worth double checking all of your settings. I would suggest that you set the resolution percentage within steamVR to under 100% - and make sure you only use FXAA - no SSAA at all.

    I have developed a little workflow that seems to go quite well for the CL650 - I use a Valve Index now, but it's pretty much the same... You will need the latest version of MoveVR

    1 Bind toggle VR to the keyboard ( I use 'v') - and in the settings leave VR disabled.

    2 Load up xplane and the CL650 - do what you need to do in the FBO. Set the passengers to arrive in one or two minutes.

    3 I have set commands to view the status of FBO actions, and to advance the passenger status to the next stage. (Ctrl-F and ctrl-P respectively)

    4 Once loaded into the sim, press the pax advance key - and wait for the phone to ring. Answer it, tell them to send the passengers now.

    5. Once you have cleared the dialogue boxes, you are free to enter VR. 

    6. When the fueller asks you to specify how much fuel you need, you may get a blue empty box appear - open up MoveVR (again, I have this bound to a key command) and open up the plugin menus, the last one in the list will be the fueller options. Click 'move to 2d'.

    7. You can then use show desktop in steam VR, or lift your headset and interact with the fueller using the menu on the screen. 

    8. Repeat that step if he asks you for anything else. (Alternate: use the 2d fuel menu to fuel the aircraft skipping the fueller stuff)

    9. Enjoy your flight! Once you land, and you are done, press your toggle VR button ('v') and then interact with the FBO to pick up the passengers.

     

    It probably sounds a bit long-winded, but it works for me every time and I've not had any big issues. Hopefully Toto will soon fix the menus so we can interact with them in VR, then the whole thing will be easy!

    • Like 1
    • Upvote 1

  9. [OPEN] CTD on start in VR, also with V1.1.0

    in Crash To Desktop

    Posted · Edited by severniae

    @Sleepy81

    I had a Pimax8KX - it worked fine with the CL650.

    Are you starting Xplane with VR already enabled, or are you clicking career / non persistent and then loading VR. Note, with the CL650 you must enable VR AFTER using this menu. Best method is to bind a keyboard or joystick button to enable/disable VR. Load it up after you leave the FBO...

    What are your SteamVR settings? Have you tried a clean re-install of it?

    Do you have parallel projections enabled (you need to)

    What are you xplane settings?

    Are you using Large, Normal, Small etc... FoV?

    What have you got set supersampling-wise?

    There is another setting, I don't recall the name, that sets between (IIRC) 0.5 and 2x - it's some form if rendering option in PiTool... what have you got it set to?

    Are you using native or upscaling in PiTool?

    Any settings configured in nvidia inspector or otherwise that affect settings...?

    • Like 2

  10. About CL650 wingflex

    in Flying the Challenger

    Posted

    11 hours ago, Goran_M said:

    We really don't mind.  If it isn't too much of a big deal to add a bit of eye candy, we're more than happy to accomodate those who want it.  I'm a big believer of the little things that make people go "Wow!"

    In saying that, I will be adding wingflex, however, it will be very subtle.  I think it flexes by about 10 inches up and down (20 inches in total), but I will confirm.  We have quite a few things on our plate at the moment, and my top priorities right now are the ADG and some external decals.  If I can fit wingflex in before the next update, I will.  

    The only thing I would say - please only put it in as it is in real life! Too many people are used to 'sim-isms' (just take a look at the debate on visibility at altitude..).

    • Upvote 2

  13. [NO RESPONSE] Crash during approach

    in Crash To Desktop

    Posted

    Crash on final, crashed immediately on pressing the button for the final checklist item. Nothing to give any idea what happened in xplane log. Even more annoying, I load the latest approach autosave, and it's my last flight, and then it overwrote the latest state too, so I can't finish. Not first time it's happened unfortunately, has happened at least once before, same circumstances.

     

    2022-01-27 16:20:33 CL650[waas_api.c:205]: Failed to download WAAS API data: server responded with error 404 (Not Found)
    2022-01-27 16:23:27 CL650[gps4000s.c:2956]: EGNOS data download successful
    2022-01-27 16:23:33 CL650[waas_api.c:205]: Failed to download WAAS API data: server responded with error 404 (Not Found)
    2022-01-27 16:23:35 CL650[gps4000s.c:2917]: WAAS data download successful
    2022-01-27 16:26:34 CL650[waas_api.c:205]: Failed to download WAAS API data: server responded with error 404 (Not Found)
    2022-01-27 16:26:38 CL650[phys.c:821]: GFS download successful, SL_T: -12.7°C  TP_T: -57.6°C TP_alt: 33258 ft
    2022-01-27 16:28:38 CL650[gps4000s.c:2917]: WAAS data download successful
    2022-01-27 16:28:44 CL650[fo_actions.c:1311]: FO actions: gear down

  14. VR Feedback/Recommendations

    in Hardware Interfacing

    Posted

    9 hours ago, sparker256 said:

    Adding this to the cl650_vrconfig.txt file has the yoke trim switches working. 

    #ELEVATOR TRIM

BEGIN_MANIP command_switch_up_down sim/flight_controls/pitch_trim_down sim/flight_controls/pitch_trim_up
DEG_PER_ACTION 7.5
HOLD_MANIP
END_MANIP

     

    Thanks! I'll add this to the config file.

  15. VR Feedback/Recommendations

    in Hardware Interfacing

    Posted · Edited by severniae

    All,

    With permission from Goran from Hotstart, I am sharing my VR Config file, and edited CL650 cockpit object.

    Just unzip and place the files in your C650 folder - make a backup of the object file prior in case you want to revert.

    https://drive.google.com/file/d/1fPhnHghObnaA-f47WavSrAy2FqDSejVv/view?usp=sharing

    Just a note - this configuration isn't officially supported by HS yet, so please if you encounter any bugs and want support, revert to the original cockpit file.

    Please let me know if you encounter any VR issues, or have any suggestions relating to the config file - I'd like to finesse it as much as is possible..

    Enjoy!

    James W

    EDIT: Link updated with file for version 1.2.2

    • Like 3

  16. VR In sitting position plane not fully rendered. In Standing position plane is fully rendered.

    in Hardware Interfacing

    Posted

    The issue I think is because HS cull any objects / textures that aren't in view - for some reason being close to the ground culls the external textures in VR, I think it's because in VR, you are never *truly* in outside view.

    Easy workaround in steam VR is to use OVR advanced settings to define an offset that moves your head position up a little.

    • Like 1

  19. VR Feedback/Recommendations

    in Hardware Interfacing

    Posted

    54 minutes ago, jrrogers said:

    @severniae Did you have a chance to look at the VR configuration for the external doors such as for fuel, oxygen or lavatory servicing? It takes quite a lot of fiddling with the VR controller to open or close these doors.

    Not yet, I will do this week.. I just noticed myself that they aren't exactly VR friendly - should be an easy fix soon as I have time..

  20. VR Feedback/Recommendations

    in Hardware Interfacing

    Posted

    12 hours ago, louism said:

    I find the chart zoom button is not working with the controllers. Is it because I don't have the latest updated files?

    Otherwise great job for all the teleport spot placements and switches, it is just AWESOME to fly the 650 in VR :wub:. The modeling, the sounds, the systems. Oh my god, simply next level of immersion!!! THANK YOU TOTO AND @Goran_M!!!! My #1 sim dream of having a biz jet finally came true in the form of the BEST add-on ever, and from no other than my favorite add-on developers of all time.

    Cherry on top is it's the Challenger and I am from Québec, based in CYUL. :P

    Thanks for the spot - I've just included some fixes for those in my config file. I'll send it over to Goran.

    I'm not going to share my updated version at the moment as it relies on changes to the OBJ file and I don't want to redistribute any of HS's assets, and I hear update 1 is just around the corner - so let's wait until that is released, and then if necessary I'll post the latest VRConfig file.

    • Upvote 1

  23. VR Feedback/Recommendations

    in Hardware Interfacing

    Posted

    2 hours ago, Eman said:

    Throwing in my support for VR...

    I've been using VR since October 2017 with a CV1 and since have never used my 2D monitor for simming (or really any gaming, TBH). I now have a Reverb G2, and it is glorious. VR is the future, and I think it's time developers stopped relegating VR to the bottom of the barrel just because it's too "niche".

    It is not. Not anymore.

    Having said that, I applaud and thank HotStart working with our VR community to get this plane "up to snuff" with respect to VR.

    I've been waiting 23 years for a business jet simulation of this caliber. My credit card is so close to being ready. But I'm waiting to see how the dev team implements VR into this otherwise masterpiece of an aircraft. In the short term, I really want to see proper manipulator spots (throttle, appropriate knob sensitivity and rocker switch manipulation, etc...) and all of the study menus become easily accessible with the VR controller. In the longer term, it would be nice if the phone, fuel truck, walkaround and FBO became VR-friendly.

    Thanks again for all the brilliant work on the Challenger. But please do a great job with VR.

    -Elliot

    Nearly all you mention is already compatible. If you use my config file, all the rocker switches and knobs work just fine. I think once thats sorted, the only thing will be the FBO 2d menus to communicate with the FBO/fuel truck etc.. then, it will be perfect!

×
×
  • Create New...