Scuby

Hi Rel4y, I'd like that. Mail sent. Cheers, Scuby

Hi all! I have just finished this mod about one hour ago! The Speedbrake switch appears more easy to mod, because it can be rotated more freely internally compared to the Dogfight/Missle Override switch. You'll kill two birds with one stone here: 1. by re-aligning the button axis with the actual switch axis inside, you'll prevent wear and ultimately failure of the plastic housing (that stiffness you mentioned is a precursor for damage) (see how it is done here: http://www.cougar.flyfoxy.com/mods.php#speedbrake), 2. the entire switch (incl. button and housing) needs to be more naturally aligned with your left hand tumb as per RL angles of the F-16 TQS. This mod required a 45 degree rotation of the entire switch to the left, and cutting its plastic housing so it would fit the internal mask again. The Dogfight/Missle Override actual switch is more limited to rotate due to two metal braces internally keeping it in an undesired position. Still, just like the Speedbrake switch I managed to align the button axis as much as possible with the actual switch, and was able to rotate the entire switch "about 15-20 degrees" right. The button axis now comes close to being perpendicular to the left hand tumb. All feels a lot more natural now and more correct to operate compared to default switch angles of the TM Cougar TQS. I'd recommend every owner to at least consider this Speedbrake mod. Also, I removed the entire detent plate in the base, the Z-axis movement is silent now and also a lot more accurate in 3D! Though, without detents I'll have to watch my FF more now for that AB kicking in :music_whistling: Inspecting the TQS, Speedbrake and Override switches all the way on the left: Close up of the Speedbrake (lower) and Override switch (upper): Cutting the plastic housing so it fits the mask at the intended alignment: The result with only the Speedbrake switch re-aligned: The result with both Speedbrake and Dogfight/Missle Override switches re-aligned: Real TQS versus my modded Cougar TQS: *Note: the TM Couger TQS is not a perfect 1:1 replica of the RL F-16 TQS, so actual switch angles may differ (and they do :) )

Hi mate! Actually, I have just finished this mod about one hour ago! https://forums.eagle.ru/showthread.php?t=278164

It was clear to me :) @MAXsenna, indeed it appears that you misunderstand, however you are also right in a way. It is like this: If a user creates the phrase "DO IT", you can not bind that phrase to all possible commands. You can only bind it to one command, i.e. results in one particular type of action in 3D. Now however, because the phrases "Request Taxi to Runway" and "Request Taxi for Takeoff" appear to be aliasses but in fact aren't by default in VAICOM, i.e. are two seperate commands, (but one of them does not exist in DCS?), it gets confusing. The result is that you are not able to create and bind "Request Taxi" to both, only to one...while they intend the same command/action in 3D. And to make it even more confusing, due to limitations in VAICOM, the user is only able to bind the phrase "Request Taxi" to "Request Taxi for Takeoff"... which is a bug. Also above, the case is being made to combine "Request Taxi to Runway" and "Request Taxi for Takeoff" into aliasses by default in VAICOM. As HILKOK states, either one of them is superfluous/redundant, or are trying to catch more peoples way of saying the same thing. Hope this helps.

In the video below I recorded flying a mission in 3D and viewing its recorded Track, back-to-back. Now, if we compare the landing sequences, it becomes clear that there is somehow a mismatch in the position data between 3D (@51:50 mm:ss) and the recorded Track (@1:02:40 h:mm:ss). What went wrong in the Track? This was recorded in Open beta 2.5.6.50321

Hi Hilok, Answer is Yes, sort of. I created the phrase "Request Taxi" and this is binded to one segment "Request Taxi for Takeoff". I was unable to bind it to segment "Request Taxi to Runway" which is a unique issue, hence my "bug/issue" report to Hollywood above. It is not possible to bind one phrase to more than one segment, in other words, I can not make "Request Taxi" bind to both "Request....Takeoff" ánd "Request....Runway". This is only possible once Hollywood changes those two segments into two aliasses by default. If there is a new VAICOM version, and DCS commands have changed too, you may want to keep a record of your own additions to the words list (use export). And adding an aliases for "Request Taxi to the Ramp" is very easy. In fact, I created an alias "Request Taxi Back" but might also create another "Vacated".

Thanks, yesterday the same issue also appeared with the mouse, so I can confirm your report as well: It appears that, for reasons unknown, that in some occasions both the VR controller and mouse are not able to activate the hotspot on the door handle of the pilot (right) door. After using the key-combo voor opening/closing front doors, it appears that both VR controller and mouse work OK with the hotspot on the door handel. This issue appears random and it is difficult to find the causes when it does.

Hello Hollywood, It appears that when in the Editor, the user is not always able to keep the intended "segment" locked to his newly created phrase: For the segment "Request Taxi to Runway" When specifically the phrase "Request Taxi to Runway" is copied by ADD NEW (Request Taxi to Runway1), Followed by editing this newly added phrase to "Request Taxi" according to recommended procedure, The segment is automatically being changed to "Request Taxi for Takeoff". I reckon that the output in 3D will be the same, however according to the manual page 54, these phrases (Request Taxi to Runway and Request Taxi for Takeoff) appear to be categorized seperately as well. I'd expect them to be combined as aliasses. Would you consider coding user ability to lock a specific segment? Cheers, Scuby p.s. I have complete VAICOM PRO / modules package.

Hello Hollywood, UPDATE: disregard this report, I have completely overlooked that there was somehow a DX button assigned to Chatter in the VA profile,... how I did not see this all this time?! consider this message not a bug It appears that with version 2.5.20.0 (release) after a period of time of having VAICOM PRO active in Windows 10, automatically the RADIO CHATTER is being activated, while this setting is disabled. This has happened to me also when DCS is active, at random times, while this setting is disabled. Could you please look into it? Thanks for this awesome tool! :D

The following issue is tested and easy to reproduce in Open Beta 2.5.6.50321. It appears that, when the user follows this sequence: user starts a flight (tested: instant action, spitfire, normandy, take-off mission), followed by ESC>Quit and exiting 3D, clicking on the menu button "view track" to watch the recorded flight in 3D, followed by exiting 3D again, ... The result is that, if the user now clicks on the button "fly again", then automatically the view track mode is still being activated in 3D (free to fly mode in 3D is not initiated in this case) and the users ends up watching his recorded flight again.

I can confirm that, even with high spec PC, this map performs much lower compared to all other maps with unchanged settings. In current state, this map appears to be too heavy or unoptimized for the PC to render VR effectively.

I confirm that even with high specced PC the VR performance is much lower compared to other maps with equivalent added assets and weather. I reckon it is still EA and it needs to be tweaked for people to be able to enjoy it in VR. I think the map performance at current state is too low compared to the performance on other maps.

Issue / Bug report: It appears, by unknown causes to me, that during some cold start situations the VR controller is not able to click/activate the pilot door handle to close the door. Only after the PC mouse has been used first by clicking on the door handle to close and open the door, then the VR controller will work OK on the door handle. This issue appears to reveal itself inconsistently, which makes it difficult for me to re-produce. Does anyone experience this issue also?

@webweaver40, to answer your question, Actually no! It was the 8KX! In the mean time there are more reviews and user experiences out there on internet saying as much about the 8KX, which I expected considering I was disappointed with the quality too. I reckon that there are also positive experiences. You certainly seem convinced that the 8KX is very good, and really I think that is great! I'm a firm believer that everybody should test a headset for themselves first, before deciding to buy. I think that is good advice. For me personally, I will not consider 8KX, because after my own testing I conclude it does not meet my requirements. Yes, there is always going to be people who totally WOW and hype it after trying it for a few minutes, and be cognitive dissonant to any contrasting views, but I will predict it here: 8KX is not going to be big with the consumers. Really, +1 for Pimax to set first foot on the moon making double 4K and large FOV financially accessible to consumers! Only do you really think it is not compromised somewhere? Why is e.g. Farjo, XTAL, so expensive? Just to tease us little people? :P I'd rather wait for them, or Oculus even, to get such specs to that "accessible" price point. A lot of 8KX consumers are frustrated now, because (again) many did not receive their 8KX yet from Pimax. It was supposed to be released already... by which I mean there is much more things to consider for a product to succeed. I'd prefer a more trustworthy supplier. Indeed HP Reverb G2 is revealed. I would be investigating and considering that much more closely, quality and feature wise; i.e. even with upcoming 3080Ti something like the Reverb G2 specs (Resolution, PPD, FOV, FPS) are going to be "sweetspot" for some years ahead. Also with the likes of an Index. Trust me on this. Don't believe me? Look at the Farjo headsets DCS is just supporting: awesome quality and clarity, but at 87 FOV not that far off the sweetspot. Try running 8KX with 2x 4K resolution at 170 FOV. Awesome if you can get 90 FPS without compromising on the beautiful DCS graphic settings... I expect you can properly by 2024 with an 4080Ti probably. Also there's some "secret headsets" underway, which do not have a reveal date,....... yet ;) .

This mod is great! I use the green Nomex Gloves version. However, it appears it is not allowed to use this texture by the multiplayer validation checker. If ED team is watching, can you guys make this mod pass the multiplayer validation checker? many thanks :D

I can confirm, that when all local P-51D engines are shut down, for all clients in multiplayer session and/or all AI in any single player or multiplayer session, the popping sounds continue. I have seen in versions upto current version in open beta 2.5.6.45317

In my opinion, go with the HP Reverb. I was able to test Index, Reverb and 8KX side by side. My conclusion is that right now Index offers the best quality and balance overall, because there is always more to consider, like sound, comfort, etc. etc. Reverb (v2) is really good too, it gives a clear picture and price is not to bad either. The Pimax 8KX was very dissapointing to me. The sweet spot was very tiny and with little head movement (try dogfighting) you keep loosing the sweet spot. What gets really annoying is that you constantly need to reach and correct your headset during flight. If not that, then the lenses were getting fogged up rather quikly. Don't get me started about the sound... I was quickly done with it. Yes, the 4K pixel density is there, however you can only see sharp in a tiny spot looking straight forward, which feels too restrictive compared to Index or Reverb, you'll want to be able to look around and see sharp, if only for a bit, to glance at your instruments or something like that. Also there still is the tiniest bit of screendoor and distorting on the outer edges. Performance in a normal DCS mission (low level, with aircraft, targets) was just terrible with a Intel 9900K and 2080Ti, which leads me to think that there is a lot of wishfull thinking that 8KX 2x 4K screens are going to bring us wonders. The Reverb is going to help you there, albeit for a lesser FOV, but at good attainable performance. It may sound as the ideal package and truly +1 for Pimax for pushing it to the consumers, but I have to recommend anybody to try to test the 8KX first yourself, before trusting and buying it. Who knows, maybe you have a far better experience than I did. I hope you do :). For the record, I own a Oculus Quest and am very happy with how it performs in DCS with Link. I also have experience through friends with Rift CV1 and Rift S in DCS, who are happy with those headsets also. Lastly, the Pimax 8KX (pre-production model) was my first ever try with any Pimax headset, so I can not compare my experience to any other Pimax headset.

The same issue with Oculus Quest with Link. It appears that some (distant) objects and shaders (observed for clouds, smoke and aircraft taxi/take-off lighting) are only being rendered for the right eye and not for the left. This was visible from the F16 cockpit looking outside and from outside view looking to the 3D world. Hope this can be fixed soon.

I can confirm this bug, with the latest openbeta release, 2.5.5.41371: When in DGFT Override Master Mode and with a contact locked in FCR (ACM BORE), if the user switches to MRM Override Master Mode, the result is that the lock is lost. This is incorrect. The correct behavior is that the lock is carried over to any other AA Master Mode when switching.

Dude, you are a life saver! Works like a charm for the F-16 ICP data control switch. Thanks! :thumbup: Also thanks to the OP for bringing this issue to the forums. I just couldn't figure out why some AHK keypresses would not give a return in 3D. Now I know. :joystick:

Yes, it works!

Wireless did work very well with DCS, but only for a while, with ALVR. Currently there is no other app or alternative. We just have to wait and hope that link is going to work! Cheers

Yes! With ALVR (free) it is possible to stream DCS to the Quest headset. The quality of the WiFi stream is great and with the 1440p OLED it appears to me and others that PC games really look visually better on it than current consumer PC VR headsets... Although, ALVR is still in alpha development, and with regards to some games, like DCS, it unfortunately shows warping/distortion when moving your head. This is known and will hopefully be fixed at some point. With Riftcat ($) it seems to work OK with DCS so this proves that streaming VR can work awesome for all PC games at some point. Another example, with ALVR and X-Plane 11 this appears to work great. In case your next question is, would you recommend it as a PC VR replacement/upgrade? Than I would probably say no with a lot of difficulty. Rather buy the Quest as a "gameboy type" console to enjoy standalone VR games with, and than see the PC streaming as a (awesome) bonus.

Thanks Sandman! I reverted drivers and DCS workes fine. I'm on Oculus Quest, streaming PC image with ALVR.

Hi! Hope somebody can help: Since the latest DCS update (v2.5.4.30386) it appears that my VR is not working. When DCS starts, it will continue to the regular 2D menu on my monitor, and does not push any image to my VR headset. I'm using standalone DCS. SteamVR is running in the background. The SteamVR window only momentarily shows DCS.exe is loaded, after which it blanks out. I'm using SteamVR v1.4.18. I checked the DCS settings menu, the option Enable VR is checked. I checked my headset, it shows and "hangs" on the SteamVR program loading animation. Does anyone have any tip to get my VR working again? Thanks :thumbup: