Morphine

Further to the OP post... When using the default shortcuts (updater.exe or dcs.exe) to launch DCS, it now launches in a "Varjo Native" mode if you are using a Varjo headset, which results in 4 screens being rendered. The 4 screen "Native Mode" screens used only by the higher-end Varjo VR-3 and XR-3 headsets which contain 4 physical screens. The more common Varjo Aero only has 2 physical screens and therefore, doesn't use the extra 2 rendered screens. Rendering 4 screens is a massive hit on the fps. Therefore, the result is a very significant degradation of of performance for Varjo Aero users for no reason. Users can currently use the "--force_steam_VR" command line argument after making a new shortcut, but they then lose the updater.exe shortcut auto check and is often causing frustration and performance hit for users. In addition as per the OP post, there is a doubling of the in-game cursors and they are out of alignment. Even worse, the dimmer of the 2 cursors is the actual functional cursor which makes this "Varjo Native" mode useless (even if one wanted to put up with the poor fps). Suggestion: Have DCS launch in the SteamVR mode as previously implemented (so that users don't have to use the "--force_steam_VR" command line) and let the small number of VR-3 & XR-3 users who want the "Varjo Native" mode use the "--force_varjo_VR" command line. Also fix the cursor alignment issue in the Varjo Native mode.

Interesting.... With my VR-3 the regular shortcut opens Varjo VR mode and I have to use --force_steam_VR to get the original Steam VR mode. I did not need to redo the WMR flip.

I found that adding the --force_steam_VR switch worked. "C:\DCS Open Beta\bin\DCS.exe" --force_steam_VR

Fair point!

@BIGNEWY Is it a real world procedure that the Bomb codes would not (could not) be changed unless the engine is off? If we have a running jet and change the loadout, it's a real pain to have to shut down to change the codes. If possible, it seems that if the jet is still on the ground we should be able to change the codes (ie. the ground crew would be able to do it at any point). Thx!

Thanks for quantifying this! I noticed that it felt much worse as well but didn't have an old install to compare to.

I want to have some VR friendly commands available while using Vaicom (e.g. Escape, F-keys, pause) but only have them triggered if I push only one of the PTT keys (TX5 or TX6) and not the other PTT Keys (TX1, TX2 or TX3). That way, if say over SRS, "you need to use the F10 key to see the map" I suddenly won't be in the Map View. I'm happy to put the commands in a Daisy Chained profile (preferred) or in the main Vaicom profile. Any ideas?

I saw something like this once when I was using a shader mod. Going back to default shaders removed the "auras" but perhaps I also changed the MSA setting.

TF-51 Canopy Question @Bailey Thanks for the great work on the profiles. I was trying out the TF-51 the other day and when I say Canopy Open or Close it would only turn the crank a small amount so one would have to issue the command many times to open or close all the way. Any idea what I am doing wrong? TIA

I like the font that is used in the ABRIS. Does anyone know what font it is and if it's available as a True Type font? Thanks!

Thanks again for all your help Lawndart! I'll take a look at that thread. Best regards, Morphine

Thanks for the centering software. My problem is more mechanical in nature as there seems to be almost two X-axis center spots... one where the stick returns to if I just release it from deflection and one where it wants to settle if I just nudge it left or right a little. So selecting one place to "center" it with software is just as valid as the other. I'm wondering if there is a spring or something I can replace to remove the second dead spot. I'm off to the interwebs to do some more research on the internals of the device.

Add me to the list of paranoid users. I also have the spot on mine but it's on the X-axis. If I deflect my stick to the right or left and release it goes to a spot just to the right of center. A little nudge and it goes back to center though. The problem is that the spot on the right is about 1500+ units from center so I'd have to have a pretty big deadzone to eliminate it. Oh well.... Thrustmaster :joystick:

I've tried to install the BS2 patch a couple of times over a freshly installed and activated version 1.0 and 1.0.1 with no success. However, I have installed BS1 on my D: drive (e.g. D:\Games\BS1). Does the BS2 installer require the standard C:\Program Files(x86)\... installation to work?

Does using the "virtual monitor" method screw up the User Interface screens for Multiplayer?

Hi Sebro, Interesting idea to get a second "virtual monitor". Have you been able to make this work with iControl? Also, I used to run a real 2nd monitor to display the MFD's and that screwed up the Multiplayer Join Screen (the UI stretches across all displays and unless the vertical or horizontal resolution is the same as your main monitor, parts of the screen are clipped off and you lose the join button for example. Have you tried Multiplayer with this iControl configuration?

I don't know why you all don't believe Baghdad Bob. http://www.youtube.com/watch?v=s27Oq5ot0ZI

IRL having the runway lights off is SOP at many airports around the world. The controller will either turn them on for you (if present) or you key your mike to turn them on (in some places you can adjust the intensity by the number of times you key your mike). http://en.wikipedia.org/wiki/Instrument_landing_system

Assuming you have both plugged in to different connections on your computer, make sure your speakers are set as your default Playback Device (Right click the speaker icon in your taskbar to get the options). Then go into TS3 and under Settings -> Options, select your Headset and Microphone under Playback and Capture options respectively. You can now start the game and you should hear all game sounds (including game AI comms) through your speakers and all TS3 chatter through your headset.

If that's possible Headspace, that would be the ultimate solution. My $0.02 on this issue is that the majority of the people using TARS are doing it to increase the realism/immersion and therefore voice-activation would be something they would be willing to give up quite easily in order to get PTT functionality similar to real world. In the meantime, I've done as you or someone else suggested and mapped both commands to my PTT buttons on my Cougar. For example, I send two keystrokes when pushing the VHF button. The first is the Radio Selection (e.g LCTl+1 [pulse]) and then the PTT for TS3 (e.g. ScrollLock [hold]). works pretty well so far. This can be programmed easily in both Target and Foxy.

Here's another converter as well: http://www.dmap.co.uk/ll2tm.htm Just make sure you use the WGS84 database and for both converters be sure to note and communicate the UTM grid zone (37T or 38T) as the area of operations spans both.

I just change it to something else (e.g. 303.5) in the ME before flying the mission and then once in the game you can change your VHF radio to 127.5 to hear the other flights.

I have them working in Beta 3. Go back to the start of this thread and follow BoredTechie's directions. If still not working, please post specific problems/questions here.

I haven't played on an MP server with integrity check turned on recently but on one ocassion a few weeks ago, I did get the "failed" message which was probably due to the snap view changes (in fairness though I have been changing other views as well so I don't know if it was the snap view changes that caused the problem). In addition, on some MP servers the snap views revert to defaults so perhaps there is a way for the server to enforce the default and not allow custom snap views while allowing the client to pass the integrity check.