Jump to content

melchionda

Members
  • Posts

    172
  • Joined

  • Last visited

Everything posted by melchionda

  1. Here is another usecase for one button doing more than one action. In the F18 when launching off of the catapult in the day you do a pilot salute, at night you flash your lights. It would be great if I could bind my pilot salute command to the toggle to flash the exterior lights. Obviously, every time that I turned my exterior lights on via the throttle switch a pilot salute command would go out, however that's not a problem because you only use that switch when you are in flight and fencing in or out on mission, and so obviously you are no where near the ship or the catapult.
  2. Im using the Viacom Pro Kneeboard feature. I think it works pretty good except I'm noticing that every time an AI talks on the radio (either to me or to another player in multi-player) the kneeboard page changes to the Viacom Pro kneeboard page. This is super annoying because for example last night I was doing an IFR flight and I really needed to reach though the procedures but the ATC at a local airport kept broadcasting to another player and every time it broadcasted by kneeboard page would change to the Viacom pro kneeboard and then I would have to page back to the one I really wanted to look at. Is this how it it supposed to work? Seems like the Viacom pro kneeboard pages should never change by themselves for any reason.
  3. I had the same issue and the way that I fixed it was that I needed to go to the Audio Tab in Viacom Pro and click the Init button. It actually doesnt really look like a button and I dont know what it does but it does fix the problem. The only problem with the solution is that I need to click the Init button every time I start up Viacom Pro. (That didnt used to happen).
  4. Ok, so clicking Init fixes the issue... but the issue keeps happening requiring me to click Init quite often. Any ideas as to why I would have to click it so often?
  5. The Init button did it! I was re-selecting the audio source but not clicking the init button. I tried also clicking the Init button and it didnt seem to do anything. I tried it like four or five times and it finally worked. It's weird how some of this stuff is inconsistent. Thanks to Max and Olmba for the help!!!!!
  6. I could see how it might be necessary to reselect the various audio devices to get audio to go through the proper paths. However the radio and voice attack communications are already flowing through the correct audio devices. In other words.... when I do a VIACOM PRO/voice attack command through my headset mic I can hear the response from the AI in my headset and the command is executed successfully. So wouldn't that mean that the proper audio devices are already selected? Is there a different setting for audio cues and notifications than audio communications?
  7. I'm looking for a camera angle in DCS that would be the view of a person on the ground along my flight path. Is there anything like that already in DCS?
  8. Thanks Olmba; but I do not think that is the problem. The audio devices were already selected and working properly for communications. The issue is the feedback and sound effects.
  9. Hi folks, I have a few questions about audio feedback and sound effects not working. Overall I have VIACOM pro working pretty well I think, but after an update a few weeks back a few things stopped working. Note that I also use SRS; Im not sure if that might have anything to do with this. 1.) Before the update when I would open up Voice Attack and VIACOM Pro would load I would hear a beep in my headset confirming that Voice Attack and VIACOM pro were now up and running. This was good because it told me two things.. first that those apps had opened successfully and second that the correct audio device was now selected. I'm no longer hearing that beep event hough the proper audio device is selected. Any ideas what setting I might need to adjust? 2.) When speaking to AI in VIACOM pro I used to get a beep response from VIACOM pro telling me that the AI was listening to me after I had called them by name. So for instance I would say "Chief"... "Remove the wheel chocks" and and some point either just after saying "Chief" or finishing my statement I would hear a beep telling me that VIACOM pro had heard me and understood what I was saying. I no longer hear that beep. Any ideas what setting I might need to adjust to get that beep back? 3.) When clicking a PTT button I would get a radio sound effect which sounded like static. I'm no longer getting that sound effect either. Any idea what I setting I might need to fix that? After reading all of this you might think that maybe I do not have the right communication audio device selected. However I do not think that is the case because I can hear all AI and real people through my headset, I just cant hear the audio feedback cues. Any help would be appreciated.
  10. Regarding binding PTTs in DCS... seems like you would have to do that if you wanted to have your radio calls to AI and real people go out over the same frequency. I've had it set that way for about a year and it works well in that my teammates can hear my radio calls out to the Tanker, Marshal, ATCs etc. The only PTTs that I would not bind in voice attack are the PTTs that I know will only be used to talk to real people. That is the adjustment I made last night and it seems to work really well. So now I have. Mic Switch 3 o'clock position: In Viacom Pro its mapped to PTT1, In DCS its mapped to Radio 1, In SRS its mapped to Radio 1 Mic Switch 6 o'clock position: In Viacom Pro its mapped to PTT2, In DCS its mapped to Radio 2, In SRS its mapped to Radio 2 Mic Switch 9 o'clock position: in Viacom Pro no mapping, In DCS its mapped to MIDS A, In SRS its mapped to Radio 3 Mic Switch 12 o'clock position: In Viacom Pro no mapping, In DCS its mapped to MIDS B, In SRS its mapped to Radio 4 Mic Switch Push In: In Viacom Pro no mapping, In DCS no mapping, In SRS no mapping, In Discord its mapped as Push To Talk Random Button on one of my button boxes: In Viacom Pro its mapped to PTT5 - I use this to talk to the crew chief as well as talk to Voice Attack / ViacomPro to select Function buttons, (ie F1 through F12). As for DCS and SRS there is no mapping for this button as its only for talking to Voice Attack / ViacomPro --------------------------- Regarding navigating the Kneeboard. I'm pretty sure that those page name calls do not work if you use the VSPX voice recognition engine. (That is the one that I was trying to use) I have since gone back to the "regular" one and its now much easier to navigate the Kneeboard. Also, I'm pretty sure that the Auto browse isn't supported if you use the VSPX option.
  11. Yes, if I am calling a Tanker then my teammates on the same frequency should hear that. And to do that I have TX1 bound in Voice attack but its also bound in SRS. (Thats how I have run it in the past). On another note, I think I have found my problem. I had TX1 in Voice Attack and Radio 1 in SRS bound to the 3oclock position on the Mic Switch but Radio 1 in DCS was bound to the 12 oclock position. I'm going to test this tonight to see if that fixes it. I bet that was my issue. I wish the pages in the Kneeboard could be called up by the name that is shown on the Kneeboard tab so you dont have to remember more stuff!
  12. 1.) Thanks and sorry, I mistyped. I am aware that TX4 is AUTO and TX5 is intercom. Also, I mapped my Mic switch the same way that the Viacom manual suggests so I was making the connection that the direction of the mic switch press equalled the TX node, however as you pointed out, that is not the case. Your response made me realize that I don't need to have TX3, TX4, and TX6 mapped in Voice attack because I will only be using those to talk to real people DataLink/MIDS and Discord. I just have to map those buttons in SRS. I'll give this a shot. 2.) Definitely not going to do it that way. One button push for PTT is how it works in the real plane and is a functional requirement. 3.) I'll try again. I tied "JAYTAK Page" a number of times and couldn't get it to work. I was using the VSPX voice recognition engine; Im not sure if that makes a difference. I have actually switch it back to the "regular" voice recognition engine because the VSPX engine doesn't support saying the name of the sender in your commands and I wanted to stick as closely as possible to the standard comms protocol and after using it for a while the inability to identify myself in my message was a deal breaker for me. 4.) I'll do some more config and some testing tonight and if I can reproduce the issue I'll post a log. Thanks for the help.
  13. Thanks! Where did you get that screenshot from?
  14. Hi, I have been a Viacom Pro users for about 18 months and I am a big fan... although I do not think that I have it set up to deliver all of its value. I have recently re-purchased it to get the new modules and I have also done a reinstall of everything so I am doing a reconfiguration. Here is my set up. Module: F/A18C Hornet Version of DCS - Open Beta SRS Thrustmaster Warthog Controls and I am attempting to use the Mic switch as follows. TX1 = Radio 1, TX2 = Radio 2, TX3 = Data Link MIDS VOC A, TX4 = Data Link MIDS VOC B, TX5 = Intercom, TX6 = Used for Discord (Push In on the Mic Switch) (This is the button in the Viacom Pro Manual recommended to turn Chatter on and off, however I don't use Chatter and I need a button to talk to my squadron team mates in Discord) Questions: 1.) In the manual it says that TX4 is reserved for the Intercom, however I need TX for to use for the Data Link voice channel MIDS Voc B. Is that going to be a problem? Instead I was going to use TX5 for the Intercom. 2.) I want to be able to do voice commands but not have them broadcast over the radios to real people. For example, I want to be able to select the "F Keys" in the comms menu, or I want to be able to talk to my crew chief to remove the "wheelchocks" or "request rearming", also the Kneeboard commands are another one that I want to be able to bring up using my voice with out having it go out over the radio. Would I use the Intercom for that? (In my case that would be TX5). 3.) I started messing around with the Kneeboard. When I have the kneeboard visible its hard to navigate to some tabs. For example, the JTAC tab and the AOCS tab are particularly difficult. Should I call them up by spelling them out (for example "Jay", "TEE" "A" SEE" Page)? Or is there another command that brings them up? For JTAC, Saying "JTAC" doesn't seem to work. Or maybe I need to train Windows Voice recognition to recognize that? 4.) In a single player session I was trying to do an inbound call to the carrier. I tuned Radio 1 to the carrier Marshal frequency and then attempted several different radio calls to the carrier using the TX1 mic switch button press. For some reason VIACOM was not hearing me. I have the audible hints turned on and so I know when a command is successful because I hear a "chirp" after I finish speaking. The calls to the carrier that were failing were not getting a chirp. I then went and looked at the Voice Attack commands list and I saw that the commands that were not getting registered had a response from voice attack telling me to "Use and active TX Node". What does that mean? Something else that is strange about this issue is that its inconsistent. I found that I could get the command to work if I clicked over to TX2 and then clicked back to TX1 and then tried the command again. All in all I was able to get it to work a few times, but it was inconsistent. I know that there is a lot there but hopefully someone can shed some light on some of these issues. Thanks so much in advance!
  15. I figured out what the problem was. I figured out that some peripherals when you plug them into your PC and open DCS they will be automatically bind to certain controls. Sometimes this is helpful. Other times it isn't. In my most recent case I built a set of driving pedals that use an Arduino Board to talk to my PC. The Joystick program on the Arduino board has a channel for rudder pedals. Im not using it but it is there. There also happens to be some noise on that channel. On a flight yesterday I saw that my rudder pedals (in the plane) were moving on their own. I went into control settings and I saw that my Arduino was now one of the controller options and it had the rudder pedals bound to an axis. I went in and deleted that binding and the rudder pedals stopped moving on their own. This is similar to what I did a few months ago for the gun trigger. I went in and deleted the other gun trigger bindings that were automatically set up.
  16. @darkman222 What is your pixel density set to in DCS? Is it 1.2? I'm thinking that Pixel Density is a critical factor here. It seems to me that 1.2 yields sharper image for me in the Hornet DDIs however my performance really suffers in that the ground under the jet stutters when I am flying low and the buildings are blurry. If I leave the Pixel Density at 1.0 performance is great but I struggle to easily read the DDIs. So I might try to go back down to 60 Hertz (Im currently at 75) and then raise the Pixel Density back to 1.2.
  17. So after I posted those screen shots in my last reply I went in and made some adjustments. I think I was able to address my bright sky / dark cockpit issue. But I also attempted to make the changes that @FETUS posted based on the suggestions that he got from Kevin but my results were inconclusive. I'll try again later.
  18. @FETUS Here is how I am set up; screen shots attached. I tried to implement some of your settings from your post but ran into some issues trying to do the Steam VR resolution that Kevin recommened. I didnt see that resolution as a choice. CPU: Intel Core i9 10900K - GPU: ASUS ROG Strix 3090 OC Edition - Mobo: Asus ROG Maximus XII Formula Motherboard - RAM: 64 GB HyperX - EK Open Loop liquid-cooling - PSU: FSP Hydro+ PTM 1200 Watt liquid-cooled Power Supply - PIMAX 8KX Headset ThrustMaster Warthog Throttle and Stick - Winwing Landing and Combat Panels - MFG Crosswind Rudder Pedals
  19. thanks so much... more than anything else... the brightness of my sky is by far the biggest problem I have. Also, seems to be happening in MSFS also... the UI in that app when in VR is kind of washed out.
  20. Thanks. Are you using 8KX? How does your sky look? If you are happy with the brightness of your sky can you share your settings for DCS Gamma, Pimax Backlight, Pimax Contrast and Pimax Brightness? I think that those are the ones that would make the difference. Strange about my signature. I can see it but I guess other people cant? Here are my specs... CPU: Intel Core i9 10900K - GPU: ASUS ROG Strix 3090 OC Edition - Mobo: Asus ROG Maximus XII Formula Motherboard - RAM: 64 GB HyperX - EK Open Loop liquid-cooling - PSU: FSP Hydro+ PTM 1200 Watt liquid-cooled Power Supply - PIMAX 8KX Headset ThrustMaster Warthog Throttle and Stick - Winwing Landing and Combat Panels - MFG Crosswind Rudder Pedals
  21. Thanks, My specs are in my signature. W/r/t settings I guess I should post screenshots of my settings for DCS, PitTool and Maybe SteamVR?
  22. I wish we could see what each of our headsets is doing because what I am seeing doesn't seem to line up with what everyone else is sseeing... 1.) I can run high settings on almost everything in DCS with no issues except when I look down at the ground and I am flying low the ground moves past in little "steps" rather than a flow. Im not sure if this is what people are calling "micro stutters". 2.) (Possible separate topic but this is a big problem for me) When I look down at the ground when I am flying low the ground right under me is blurry. Its almost like every object has a double image. 3.) (Possible separate topic but this is also a big problem for me) The sky is super bright and no matter how much I adjust gamma I cant fix it because if I adjust the gamma so that the sky looks good then the cockpit is super dark. 4.) I don't get much of a performance boost by switching from 75 to 60 hertz. The "steps" that I mentioned above are still there but maybe a little smaller. What I do notice is that when I move my head quickly around the cockpit it seems laggy. So I switched it back to 75. 5.) Smart smoothing made a big difference for me. It solved two problems. First it solved my issue #1 above in that it made the ground move much smoother (no more little steps). It also solved issue #2 in that I can now see things on the ground very clearly. The double image is gone. I would love it if someone could tell me what I am doing wrong to make my sky so bright as to make DCS almost unplayable.
  23. Hi Miles, I placed a pre-order in January of this year. I got an email confirming my pre-order at 8:48AM PST on January 22nd. The email did not indicate what my number was in the queue. Where can I find out what my number is and what do we think the eta is on my PointCtrl kit? Thanks Sean
  24. So after a minor error which scared the heck out of me I have updated the firmware. For future reference you can actually install the firmware for the 8k+ on the 8KX! I know because I just did it. After doing so PiTool could no longer "see" my headset. After a few minutes I figured out what I did wrong and ran the upgrade process with the correct firmware. Eventhough PiTool could not "see" the headset I was still able to install the correct firmware and my 8Kx now works again. I also switched over to 60Hertz. Looking out of the side of the cockpit at the ground the movement appears a little smoother but not perfect. The "steps" appear smaller but every now and then there is a bigger "step/jump". That issue aside.... What would be the negative reason to switch from 75 hertz to 60 Hertz? It's my understanding that at 60Hertz the headset is attempting to update the image 60 times per second. At 75 Hertz its attempting to do it at 75 times a second. Thats only a 15 cycles per second difference. If that difference makes it easier on the system then I don't see why I wouldn't move to 60 hertz. What would be the down side to moving to 60 hertz? Will the image not respond as quickly to head movement?
  25. Thanks for the info. I have FPS VR but haven’t looked at it in a while. I’ll check it again. I think I’m currently running at 75 hertz. I’ll try 60 to see if that makes things smoother. Where would I make that change? SteamVR? Or. PiTool? With a Strix 3090 and an intel core i9 10900k at 5.1 on all cores I’m not sure that upgrading hardware is going to give enough additional performance to be a noticeable difference.
×
×
  • Create New...