It works for me with my quest 3 but the 3d view projects across both of my monitors and behind the mfd extractions while in vr. So with AR I can see the mfds but doesn’t look so good with image behind them. There is probably a solution to it but I haven’t found it yet.
Posts made by TeeSquare
-
RE: RTT and VR
-
RE: No Nav points and lines on the HSD
You might have a duplicate or incorrect callback assigned to your device. Maybe it is also rotating the EGI knob when you think it is changing the HSI modes.
-
RE: TASMO or AGM84 fails?
I did a test a while back with 24 aircraft shooting AGM-84As at a Kuznetsov and it took 39 hits before the Kuznetsov sank.
-
RE: Fragments from the explosion: how high to fly?
Blast fragmentation radius grows to 3,700 feet over 7 seconds for most of the bombs last time I checked.
-
RE: Stick Unresponsive during takeoff
Check that your brake peddle axis are not reversed. Try to taxi around with brake peddle off and on to test.
-
RE: The Map Switch on the Avionics Panel
The map switch is not implemented.
-
RE: That massive EXIT button...
Happened to me many times making TE’s for testing things. Easy to be in one window and think that the space next to the exit button is a clear spot to drag a window and bam, exit the TE and lose your work.
-
RE: 4.37 MFDE extract HUD to MFD
I use both RTT and MFDE for that reason. Use RTT for what it can do and MFDE for what is left that it can do. Maybe one day RTT will do as much as YAME used to do so that only one program will be needed.
-
RE: 4.37 MFDE extract HUD to MFD
RTT is in this location
C:\Falcon BMS 4.37\Tools\RTTRemoteThere is a readme.txt file to help get it set up. There are also instructions on what to do in the RTTclient.ini file.
Back up your RTTclient.ini file when you get it set up because in the past it has been overwritten during updates.
-
RE: Game Not Saving My Controllers
The Alternative launcher might be overriding your settings. If you prefer to use settings in the setup screen then there is a little box on the AL screen where you launch the sim that can be clicked to not let AL over ride your settings.
-
RE: Threat Guide
@Icer Thanks for the kind words. CriticalMass is correct. The Threat Guide is in the Docs folder now. When there are new versions, they will be released when BMS updates occur.
-
RE: Warthog Parts
I contacted them several years ago when my throttle stopped working. I was past the warrantee time. They were willing to sell me a PCB with no guarantee that it would fix the problem. They said that connecting it would require some soldering.
-
RE: awacs does not answer
Check that the frequency on UHF channel 6 is correct. The briefing will have a comm ladder with the awacs tactical frequency. The comm frequencies need to be loaded into the dtc for channel 6 to work, otherwise it will need to be entered manually.
-
RE: Radar cursor not working in campaign mode - other modes work perfectly
Are you on the ground when you go into campaign 3d?
-
RE: Tanker patrol
Click on steerpoint 5 and select Fuel for the action. At the bottom of the window you can set the duration. It should automatically appear the same in steerpoint 6 if the action for steerpoint 6 is also set to Fuel.
When adding a package with the roll set to refuel, it should automatically set 2 steerpoints to Fuel and set a patrol duration of 5 hours.
-
RE: manual trim test and stores jettison issue
The key file at your link has the AFE… call backs set to keyboard ctrl up, down, left, right arrows not dx buttons.
Try pushing those buttons and see if the needles move while the TRIM/ AP DISC switch is set to DISC.
You can program those to your HOTAS but that will cause you other problems. shifted keys get stuck on press and hold buttons.
You need to assign the AFE… call backs to your HOTAS stick trim button.
DX assignments look like this but your button numbers will vary depending on what order your devices are loaded in.
AFElevatorTrimUp 0 -1 -3 0 0x0 -1
AFAileronTrimRight 0 -1 -3 2 0x0 -1
AFElevatorTrimDown 0 -1 -3 4 0x0 -1
AFAileronTrimLeft 0 -1 -3 6 0x0 -1 -
RE: manual trim test and stores jettison issue
For the stick trim check that the callbacks in your key file are correct. The MAN TRIM panel call backs will seem like your trim is working but you will be using the panel to make trim inputs instead of the stick. This is why the disc switch will not stop the trim inputs during ramp start.
For the stick trim:
AFElevatorTrimUp
AFElevatorTrimDown
AFAileronTrimLeft
AFAileronTrimRightFor the Man TRIM panel:
SimTrimRollLeft
SimTrimRollRight
SimTrimYawLeft
SimTrimYawRight
SimTrimNoseUp
SimTrimNoseDown -
RE: Overhead question
The AI tend to fly a tight echelon formation after a call is made for an overhead approach. For the AI to break in the opposite direction that you do, you would have had to have made your break into the formation which is not a good idea.
I tested this and the AI will break into lead after lead breaks whether they are on the left or the right. You can change the direction that the AI breaks by telling the flight to switch sides.
So if the AI line up echelon left, they will break right. If you tell them to switch sides so that they are echelon right then they will break left.