Occasionally at the end of the mission it will funk out on me and the screen on the monitor will be way too large and can't navigate it, have had to kill it with Alt+ F4 a couple of times but no big deal I don't lose anything in the process. No real issues using the VR Mod, it is working well for me. All of that of course has to be done on desktop and not in VR which is fine as those things I would prefer to do on my desktop anyway. I am getting more into the weeds of it now, with claiming salvage, negotiating contracts for higher pay, scheduling Mechs to be repaired, purchasing Mechs, etc. That was getting old quick so glad there is a way to point and click to navigate the menus. Also I have gotten better at navigating the menus without having to control a person moving all throughout the hangar. Now I am about 7 missions deep into the single player campaign and having a great time. Granted many of those hours early on were spent just doing instant action to try and get the hang of it along with adjusting my VR settings for my best experience. Well I already have 60 hours into this game and am loving it. Not going to stop me from playing as the Mech action in VR is so fantastic, but it does put a damper on the game for me so to speak. Too convoluted navigating and getting Mech set up imho. When Mission 3 launched I was yet again in the Javelin ugh. Or maybe there is a way and I am just not seeing it?Īm on the third mission of the campaign - I had taken leave to repair the Javelin after the last mission, and it got repaired and not only that showed my Centurion was fully repaired - so I selected the Centurian - or so I thought. Just give me menus to select what part I need, ie Mech Repairs, Mission choices, getting leave whilst Mech being repaired, etc. Moving in first person view going up and down stairs in the Hanger to get to where one needs to do things is a big pain in the butt imho. I have started the single player campaign and I do not like how one has to navigate through the sections. Howto: Implement copilot announcements, including V-speed callouts.I will say for the most part I am absolutely loving this game and it is gorgeous in VR for sure. Do note that the values in the latter property are in a range from 0 to 1!! If you don't need such "complicated" calculations, you can use /controls/flight/flaps instead. Since it is not sure that the pilot checks the V-speeds with the flaps in takeoff configuration, this setting must be set in a special property: /instrumentation/fmc/to-flap. For calculating the V-speeds used in this script, the FMC must know the takeoff flap setting. This script is based on a Boeing 747-400. _setlistener("/sim/signals/fdm-initialized", vspeeds) Įach aircraft has different formulas for calculating V-speeds. _setlistener("/sim/signals/fdm-initialized", vspeeds) For YASim # Only start the function when the FDM is initialized, to prevent the problem of not-yet-created properties. Setprop("/instrumentation/fmc/vspeeds/V2",V2) Setprop("/instrumentation/fmc/vspeeds/VR",VR) Setprop("/instrumentation/fmc/vspeeds/V1",V1) # Export the calculated V-speeds to the property-tree, for further use # Retrieve total aircraft weight and convert to kg. # Create/populate variables at each function cycle # Create initial announced variables at startup of the sim
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |