October 26, 20169 yr Wondering if anyone has had success in VR land, using ezdok? I read awhile back there were issues with it and with vr, i cant seem to find where i saw that or what those issues were? I'm thinking if it did work, that in conjunction with DWVAC voice commands to trigger various views might be quite good. Thanks in advance Asus Strix z790-e; 1000 watt evga SuperNova Plat; 14900k AC_LL 0.55 adp -0.050 253/253/355 CEPoff (CB-1pass 39200 80c, msfs peak 92,avg 60-78c, astrorender 95c,room76F); 64GB(dual 32) cl32 6400 at 6400 xmpII F5-6400J3239G32GX2-TZ5RK, Asus Ryuo III 360mm; Thermaltake v51 Case; Gigabyte 4090 OC; VR-Crystal; Dofreality H6; Astrosite
October 26, 20169 yr With FlyInside I just use the native view controls in P3D, and add hotkeys in the various aircraft.cfg files. P3D lets you define up to 10 keys for switching to specific views, and you can assign each key to a specific view by editing the aircraft.cfg files and adding the line HotKeySelect = X to a camera definition. For example: [CameraDefinition.001] Title = "Right Seat" HotKeySelect = 2 Guid = {195EAB58-9E4A-1E2A-A34C-A8D9D948F078} Origin = Virtual Cockpit MomentumEffect = Yes (etc.) So when you press hotkey no. 2 it will switch to the right seat view in that particular aircraft. And then you can of course also use voice command software to trigger hotkey no. 2 if you say something like "Computer: Teleport me to the co-pilot seat, please" or whatever is meaningful and appropriate.
October 28, 20169 yr Author With FlyInside I just use the native view controls in P3D, and add hotkeys in the various aircraft.cfg files. P3D lets you define up to 10 keys for switching to specific views, and you can assign each key to a specific view by editing the aircraft.cfg files and adding the line HotKeySelect = X to a camera definition. For example: [CameraDefinition.001] Title = "Right Seat" HotKeySelect = 2 Guid = {195EAB58-9E4A-1E2A-A34C-A8D9D948F078} Origin = Virtual Cockpit MomentumEffect = Yes (etc.) So when you press hotkey no. 2 it will switch to the right seat view in that particular aircraft. And then you can of course also use voice command software to trigger hotkey no. 2 if you say something like "Computer: Teleport me to the co-pilot seat, please" or whatever is meaningful and appropriate. This will prove very useful thanks for the tip Still, I'm thinking I may miss the shake effect of ezdok, however chase plane is coming Asus Strix z790-e; 1000 watt evga SuperNova Plat; 14900k AC_LL 0.55 adp -0.050 253/253/355 CEPoff (CB-1pass 39200 80c, msfs peak 92,avg 60-78c, astrorender 95c,room76F); 64GB(dual 32) cl32 6400 at 6400 xmpII F5-6400J3239G32GX2-TZ5RK, Asus Ryuo III 360mm; Thermaltake v51 Case; Gigabyte 4090 OC; VR-Crystal; Dofreality H6; Astrosite
October 29, 20169 yr Author With FlyInside I just use the native view controls in P3D, and add hotkeys in the various aircraft.cfg files. P3D lets you define up to 10 keys for switching to specific views, and you can assign each key to a specific view by editing the aircraft.cfg files and adding the line HotKeySelect = X to a camera definition. For example: [CameraDefinition.001] Title = "Right Seat" HotKeySelect = 2 Guid = {195EAB58-9E4A-1E2A-A34C-A8D9D948F078} Origin = Virtual Cockpit MomentumEffect = Yes (etc.) So when you press hotkey no. 2 it will switch to the right seat view in that particular aircraft. And then you can of course also use voice command software to trigger hotkey no. 2 if you say something like "Computer: Teleport me to the co-pilot seat, please" or whatever is meaningful and appropriate. Actually, had a question.. what is exactly meant by hotkeyselect =2 in this case.. does it mean num pad 2 or does it "point" to something say in the cameras.cfg.. or does it point to camera "2" in the controls options under view camera 2 etc.. i cant seem to figure it out.. for instance if for camera 2 i try to assign it num pad 2, its already assigned, so i dont think this is correct.. It would be better if given functions could be set to combinations of key-presses.. not just for cameras too. Asus Strix z790-e; 1000 watt evga SuperNova Plat; 14900k AC_LL 0.55 adp -0.050 253/253/355 CEPoff (CB-1pass 39200 80c, msfs peak 92,avg 60-78c, astrorender 95c,room76F); 64GB(dual 32) cl32 6400 at 6400 xmpII F5-6400J3239G32GX2-TZ5RK, Asus Ryuo III 360mm; Thermaltake v51 Case; Gigabyte 4090 OC; VR-Crystal; Dofreality H6; Astrosite
October 30, 20169 yr Author Actually, had a question.. what is exactly meant by hotkeyselect =2 in this case.. does it mean num pad 2 or does it "point" to something say in the cameras.cfg.. or does it point to camera "2" in the controls options under view camera 2 etc.. i cant seem to figure it out.. for instance if for camera 2 i try to assign it num pad 2, its already assigned, so i dont think this is correct.. It would be better if given functions could be set to combinations of key-presses.. not just for cameras too. I think i got it.. apparently only 5-9 are assignable via controls.. so i guess if i make say left wing be hotkeyselect = 5 and find some free combination of key presses i can then trigger left wing from the vac builder software. A little quirky though. And.. all this has to be done per aircraft.. perhaps there is a way to do it in another cfg file that doesnt involve changing every single aircraft.cfg but rather a global setting? Asus Strix z790-e; 1000 watt evga SuperNova Plat; 14900k AC_LL 0.55 adp -0.050 253/253/355 CEPoff (CB-1pass 39200 80c, msfs peak 92,avg 60-78c, astrorender 95c,room76F); 64GB(dual 32) cl32 6400 at 6400 xmpII F5-6400J3239G32GX2-TZ5RK, Asus Ryuo III 360mm; Thermaltake v51 Case; Gigabyte 4090 OC; VR-Crystal; Dofreality H6; Astrosite
Archived
This topic is now archived and is closed to further replies.