Hillman

Hi, Just started the campaign and really like the story so far. On mission 4 and 5 there is no ammo loaded for the gun. Is that how it's supposed to be?

Could we please have the radio (COM1, COM2) Push-to-talk buttons work as toggles like for most other modules? It's very convenient when you want to get rid off the communication/radio menu on the screen as the buttons are normally on your hotas.

I get this problem often even though I'm not jumping to the back-seat. Anoying when you try to study some feature etc....

I would really try to get hold of VD. The latest version with built in OpenXR support has been a big step up. Much less hassle, quicker load, better performance on latency and fps, better clarity. A huge step up from previous versions relying on SteamVR or OculusVR. A big thanks to Ggodin and Mbucchia for this fantastic software.

Same problem here! A bit annoying...

Same problem here. Everything looks fine until just before touchdown on the SC. Overshoots with a few meters in 4 of 4 attempts. Used the Marianas CASE III Instant Action mission. Maybe to windy? I have the burble off and I'm using OB MT 2.9. The F-14 ACLS is supposed to work with the SC now? ---- Edit: Created my own mission with 0 wind and got the #2 wire 2 of 2 tries. So maybe the Marianas instant action mission was too windy....?

Tried the mission again and the coordinates given worked perfectly for the PP JSOW. Direct hit on the 4. hangar. I guess on my first try I might have been a bit marginal on the range. In my opinion it's much more efficien to drop the last JSOW using preplaned mode and punch in the coordinates directly since the PP already uses the DD.MM.SS.ss format given in the message. So the only issue was the mixing of the words Latitude and Longitude in the message.

I will try again to see what went wrong. To me it looks more natural to use PP mode instead of adding a new waypoint.... Surely that is why PP mode exists? My point was simply there is no North indication for a longitude position. They only exists on latitudes. Equally there are no eastings on latitudes. They only exists on longitudes. You simply need to swith the text here. In your own video you enter the latitude first (N 44 etc) and then you enter the longitude (E 43 etc) No big deal when you enter Waypoints in the Hornet because you never specify if it's longitude or latitude, but on PP JSAW you do. Anyways I of course swithced this around my self As for the space, yes I was playing the one without refueling. Looking forward to the rest of the campaign and has also RoPL installed and waiting

Hi. I tried to enter the coordinates into the final JSOW in PP mode. The bomb hit some trees outside the airfield. Not sure why PP should not work? I tripple checked coordinates and elevation. I was in range and all looked good until the last seconds... And I wonder if you are mixing up Longitude and Latitude in the message that pops up? Longitudes are always east-west while latitudes are north-south as far as I know.... Also I was not able to remove the messagebox by pressing Space.

Hi, Yes, agree that ziplip is too boring. And it's nice to "get to know" the characters a bit. Maybe a little less gung-ho attitude would be more realistic though... By the way my wingman was shot down in the last mission and a few minutes later he started to talk to me on the radio on the way home . Are you saying that after talking to the JTAC coordinates will appear magically on the CAS page? I was not aware of this and will check it out again. Thanks for that tip. All in all a great campaign with a lot of memorable moments. Looking forward to your next!

Completed M14 - "Train strike" today and I have some feedback on the campaign in general. It's a interesting story and have the potential of a great campaign, but unfortunately it lack's a bit of polish and QA. QA: For example the frequencies/channels; Often channel# or frequency in messages are not correct. I think mostly they are correct in the kneeboards, but this creates confusion. In mission 14 the IP (4) and Target (5) waypoint must be incorect in the kneeboard? Should not WP #4 be the target? The JTAC missions are hard because the coordinates disappears too quickly and drowns in all the AI chatter. When in VR it would be good to put up a message on the upper left corner with coordintes like GroundPounder does in his campaigns. Often the oposition is quite overwhelming, maybe because the AI on my side is often not doing a good job... Some of the voice acting is a bit over the top in my opinion. Some joking/banter is ok, but it's a bit unrealistic sometimes here I feel. Very good to have campaigns for the Harrier and I do recommend this one. A bit of extra attention will make it more enjoyable.

Well, it definetly did not follow the laser (assuming having the TPOD cursor following the target also means that the laser is following the target) The bomb landed somewhere near where the cursor was when I pressed the TDC depress for designation. So it's a bit confusing though I now get it to work mostly. Not sure if it's me or DCS that's not consisten I also see that when pressing TDC designate the track mode sometime change from PTRK to ATRK... Why is that? Should you designate (TDC depress) before or after setting up the point track (Auto Acqu Depress)?

Just realized what I was doing wrong: I fixed the moving target to a point track so the cursor (in PTRK) followed the target. After that I pressed the designate button. In this case I then need to use TDC to pickup the target again. So it seems like one should first designate (close to the target) and THEN aqcuire the target in a PTRK mode. Then it works for me.

Hi, I have problems targeting a moving target with a laser guided bomb. I have set the TPOD to auto-lase (ALAS) and continous lasing (CDES) and manage to get a Point-track to follow the target. I also have hit the designate (TDC depress). However the bomb hit at the point where the target was at time of designation even though the TPOD is following the target and all looks ok. What am I doing wrong?

No, they are working alright. Might be that I pressed them before being told so. Will test again tonight.

Great to see the module being improved and maintained. Just started to learn it. In the first tutorial I'm asked to release the breaks by pressing W. I have bound wheel breaks to the pedals and no matter how much I press W or the pedals I can't advance. I also released the handbrake, but nothing helps. Any ideas?

With the Pico 4 and VD I find the Oculus runtime slightly more performant. What's more important though is that OpenXR places me at the wrong position (ca 1.5 meters too high) This can easily be corrected, but annoying still. Maybe issues with my PC, but don't know where to look. Also when exiting DCS I'm back in SteamVR world which again I need to exit to get back to Windows. Also annoying as I have nothing to do in that VR world... >If you have issues with OpenXR and the Oculus runtime (or perhaps Virtual Desktop), you need to report them to Oculus or to GGodin, I fully support OpenXR being the way forward. Unfortunately reaching out to VD or Pico/Bytelab resulted in no response for me...

Very strange. It works for me wether I'm selecting a shortcut or point it directly to the DCS.exe... Maybe something to ask on the VD Discord. It's described in the VD documentation. What you miss is that DCS will run in SteamVR mode instead of Oculus mode. I think Oculus mode is marginally more efficient. And when you close DCS you are back at the windows desktop instead of in SteamVR world which might be a benefit... or not depending on you usage

VR is challenging for sure and it's obviously early days... I often just need to restart/reboot to get things working. Very hard to figure out why it's not working. A couple of points to look out for: - before starting VD make sure Windows has done it's things on downloading/installing updates as this seriously slow down things. - check in the VD menu (once you are in VR double-tap the LH controller button on the very left I think) that you have both 1200Mb shown on the top and a bit-rate of 150 under the streaming settings. I often find that the bit-rate is between 10-40 and I then have to restart the headset if so. I don't think there is any difference between --force_enable_VR and ticking of in the menu to be honest. I just have it as part of the shortcut by default It seem like just starting DCS within VD by double-click directly on the DCS icon will launch it in SteamVR mode. If you right-click on the tray-icon and select "launch game" it starts in Oculus mode (for MT you need to disable OpenXR in the Registry). Right-clicking in VR is cumbersome to this can more easily be done with the short-cut: "C:\Program Files\Virtual Desktop Streamer\VirtualDesktop.Streamer.exe" "C:\DCS World OpenBeta\bin-mt\DCS.exe" Again I have this attached to a voice-command in VoiceAttack to make it very easy. CPU bound in main thread should imply that your GPU is now working smoother so the CPU is now the bottleneck (I would think :-)) RTX 3070 is probably a stretch for DCS/VD/Pico4 to be honest... I previously had a 3080 and struggled a lot. What is VD recommending for 3070?

Did you start DCS with a short-cut this way:? "C:\Program Files\Virtual Desktop Streamer\VirtualDesktop.Streamer.exe" "C:\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR Or right-click in the VD tray-icon down far right and select "Launch game..." and navigate to your dcs.exe.

Hi, remember if you remove the OpenXR support with the regedit change you should NOT use —force_OpenXR, just the —force_enable_VR. To explain a bit: this line: REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1 /v ActiveRuntime /d "None" /f basically tells DCS (or any other game/software) that you computer don't support OpenXR. This forces DCS to use OculusVR. (which some finds a better option. This is only needed if you run the multi-threading DCS version. The ST it defaults to Oculus anyway if you have a headset like Pico 4. Why they changed this in the MT version I'm not sure. Probably because OpenXR seems to be the future standard.) When I want to run MSFS (or any game which requires OpenXR) however I need to enable OpenXR again because MSFS don't support Oculus directly. This line: REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1 /v ActiveRuntime /d "C:\Program Files\Steam\steamapps\common\SteamVR\steamxr_win64.json" /f tells MSFS that my system supports OpenXR and it's handled by the SteamVR runtime. So you must decide if you want to run DCS in OpenXR mode or Oculus mode and the set you parameters and registry accordingly. By using bat/cmd files and VoiceAttack (highly recommended if you are into VR) this is fairly effortless once you have everything in place. A nice thing with VoiceAttack is that it already runs with admin privileges so it runs the regedit-changes fine. (Maybe I confused some with this line: REG QUERY HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1 /v ActiveRuntime I left that in the script just to check visually that everything works as expected. You can ignore that line and if you want to use it you need a "pause" command on the next line to be able to see the results anyway) Do you start DCS by specifying dcs.exe as a parameter to the VD streamer? If you do this you and you have disabled OpenXR as explained it should start in VR in VD. You should not even need the —force_enableVR parameter (but no harm to include it). Try this line in your cmd/bat file or shortcut: "C:\Program Files\Virtual Desktop Streamer\VirtualDesktop.Streamer.exe" "C:\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR Regarding BAT-files and CMD-files: There are some technical and historical differences, but for this case they are the same. They are both executable, scripting files. Use whatever you like.

How is it not working? Any error-message....? Paste the two lines below into a file called for example "SetRegOculus.cmd" : REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1 /v ActiveRuntime /d "None" /f REG QUERY HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1 /v ActiveRuntime Save the file and double-check the name. Right-click on the file and select "run as admin" The other two lines is to set the registry back to OpenXR again.

You need to change the registry again unfortunately. I created a two bat-files for this and you see the content of both below. First line line switches the mode. Second line is just for info and can be helpful if you have issues. Note they need to be run in Admin mode. You might need to adjust paths for your setup. I run everything with VoiceAttack (running in Admin mode) which dose the registry switching and starts VirtualDesktop and DCS. It makes things a lot easier. Included a screenshot for those interested. REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1 /v ActiveRuntime /d "None" /f REG QUERY HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1 /v ActiveRuntime REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1 /v ActiveRuntime /d "C:\Program Files\Steam\steamapps\common\SteamVR\steamxr_win64.json" /f REG QUERY HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1 /v ActiveRuntime

https://mixed-news.com/en/pico-4-now-offers-full-openxr-support-why-this-is-important/ https://www.picoxr.com/magic/eco/runtime/release/63eda4b428f1c3044230f7d3?appType=picoglobalwebsite&magic_page_no=1 I can't get it to work without SteamVR when running OpenXR-mode though so I can't see any changes after this was announced.

Are you using Streaming Assistant? Tried it several month ago with not the best results, but will test again - I see there is a newer version of SA now. Any tips on settings? Do you need to download any specific drivers etc? I'm using Wifi6 now, but do you think USB gives better bandwith?