Jump to content

melchionda

Members
  • Posts

    172
  • Joined

  • Last visited

Everything posted by melchionda

  1. Does anyone find it strange that Wingsweep on the F14 is not one of the Axis Commands? On my Thrustmaster Warthog Throttle I have a slider next to the throttle for "Friction". I don't have it mapped to anything and its perfectly positioned to be a Wingsweep for the F14 but in DCS They want you to map Wingsweep to a button. Am I missing something here? Has anyone been able to map Wingsweep to something that slides? Also can we close the Wingsweep safety cover using a mouse or do we have to map that function to a button? I can see it in VR, and mouse over it but cant seem to interact with it unless I map it to a button.
  2. I checked again last night and its still not working for me. I have the latest version of Viacom Pro installed. I gotta say, I dont think any aspect of ViacomPro is working for me at all. I've spent hours working on it.
  3. I am having this problem but I have not solved it yet. I'm new to DCS and Viacom Pro. Question... What is the process for updating Viacom Pro? Will I get prompted or do I have to manually download and install it?
  4. Hi guys, I have the F14 module, as well as Voice Attack and Viacom Pro. I was looking forward to running the guided set up with my Rio running through the checklist and me responding via spoken word "Check". It doesn't seem to work for me though. Do you have to configure that in the Viacom Pro profile or is it already set up in the profile?
  5. I too would love to see just a pure checklist start up. Interacting with the RIO is great but the "boxes" are terrible. They make it hard to see the switches and I wish I could turn them off.. or at least DCS could re-design them. Right now its a poor design that is counter productive.
  6. I find often its difficult to see which switch the box is attempting to draw your attention to because the box is so much bigger than the switch. Ive been in situations where it was tough to tell which switch was in the center of the "box". Another time its difficult to see is when it is highlighting several switches right next to each other. This happens in the A10C, especially when they are highlighting multiple buttons around the MFCD's.
  7. I am a professional software UI product designer and I totally agree here. The highlight boxes could be much better. Temporarily highlighting just the switch with a colored over-lay would be much better.
  8. Does anyone use the Maverick for Air to Air? Every now and then I'm on a mission where there is a red aircraft flying and I'd like to take it out but its to far for the Sidewinder. Are we supposed to use the TGP and the Maverick for that? I've heard that the Maverick is too slow and is often not successful for Air to Air and that I should save it for a ground target. Anyone use Mavericks for air targets or is that not recommended?
  9. Do you toggle labels on and off during the session? How do you do that? Do you have to pause the mission or can you bind it to a key stroke? If you can bind it to a key stroke and turn on and off with out pausing the action I might do that. I want realism.. but sometimes I get stuck and rely on the label "dots".... but I'd like to get used to not having to do that.
  10. In case folks are not aware of this...I've noticed (and read this too) that the D can lock up a target from farther out than some of the other Mavricks... so I always opt for the "D"s when setting up my load out. In my experience a "D" can lock up a target at the max distance, ( I think its like 11 nm), however some of the other ones struggle at more than 6 nm.
  11. Yes, exactly. That is a good way to describe it. I'm not sure if I am going to install yet another mod. I really try to keep my installs stock as possible. Its one of my gripes with DCS. Requires a ton of mods and hacking to get it to work properly. I think that this impacts their bottom line. I dont mind spending the time to read up on and learn the ins and outs of the CDU in the A10C but I definitely do not want to spend so many hour installing mods an programing my computer to get DCS to run right. Its particularly painful for me because I am a Product Designer by profession.
  12. I think you mis-read my post... The Gamma setting is in DCS, not PiTool. I tried to make that clear in how I formatted the post. However, since you responded I am curious.. when you say Contrast works fine for you what do you mean by that? Did you try moving the contrast slider all the way to the right and then all the way to the left? It took me a while to figure this out. To see its effect I had to move the slider all the way to the right, saved the setting then shut everything down and restart PiTool, Steam, then DCS, Checked the image... then moved the slider all the way to the left, saved the setting, shut everythind down, restarted pitool, Steam and then DCS. Only after doing those steps (while also making sure not to change everything else) did it seem like the Contrast slider in PiTool was inverted. However w/r/t balancing the settings in the HUD vs the cockpit in the 8K+, I think attempting to find the right settings by leveraging experience in a 5K is probably like comparing Apple to Oranges. Really hoping someone with an 8K+ has some insight on this.
  13. I've been playing around with these Contrast in PitTool: It was originally set at 0, but in an attempt to make the HUD more visible I've moved it to -2. Strangely when I was increasing the contrast things got more "washed out" which I would consider "less" contrast. So its the opposite of what I thought it would be, Brightness in PiTool This one worked as I expected. Increasing the brightness made the world in DCS more bight. I have it now set to -1 Gamma in DCS At first I had it at 1.8... then 2.2. Weirdly, increasing the gamma seemed to decrease its effect. ie- things became more washed out at higher Gamma. At Lower Gamma the cockpit got too dark. Unless there is some setting combination that I've yet to find this seems to be a compromise between being able to see the hud symbology against the sky vs being able to see the details in the cockpit. I'd be interested to hear if there is a set of settings available that can thread that neddle. Sean
  14. hi folks, I'm not super happy with the visibility of the hud symbology in the A10C using my Pimax 8K+. For me the sky has too much white glare and looks really washed out. The hud symbology is lost in all the glare of the sky. What I'm hoping for are some settings to make the sky color darker so that there is more contrast with the hud symbology. Does anyone have good settings for that?
  15. Now that I'm getting proficient flying the A10 by myself on solo missions I'm interesting in joining some multiplayer servers, but dont want to screw up too badly and look like a complete idiot... A few things I worry about... 1.) Getting "in the way" of someone else. 2.) Taking off or landing at the wrong time or in the wrong direction 3.) Boadcasting my Comms menu voice commands across the whole multi-player server. I'm interested in three things.... 1.) A good guide on how to talk on the radio? Specifcally something that could be downloaded? 2.) Maps of all of the airports? When I spawn at a new airport I cant every find my way out to the runway. 3.) Automatic kneeboard gnerator with the airport map, radio frequencies, tacan settings... etc? (IS thee such a thing?) Sean
  16. Thats sort of the opposite issue.. specifically the comms menu appears by itself due to a corrupt lua file. I had that issue too but resolved it by deleting my lua file. Just to bring everyone up to speed. I have everything (PTT + comms menu + voice attack) working perfectly and exactly as I want it to work in the A10C. I just cant get that same behavior in the F/A-18.
  17. Here is a question that may help get more to the issue... Is anyone able to get the Comms Menu to appear automatically when they push their PTT button in the F/A-18?
  18. Thanks for your reply... But the goal here is not to have to say "Options" every time I want to use the radio. In the A10C I dont have to say options. The menu just appears when I start to use the Mic Switch. I recently re-set the lua code for another issue, I guess I could try again. However seeing that this works as desired in the A10C wouldn't that suggest this is a settings issue and not a lua code issue?
  19. Thanks for the info. So are you saying that you memorize the frequencies for all of the other assets in every session when you fly? I would imagine that some people not using VR might write them down on a piece of paper for the flight, however I am using a VR headset so that's not an option. A kneeboard would be nice, but preparing a kneeboard every time I want to fly is a lot of extra work. I really just need the comms menu in the F/A18 to work the same way it works in the A10C and I'm on the hunt for why its different. I have a ticket logged with DCS and have sent them some demonstration tracks. Should be interesting to see what they come back with.
  20. It would be nice if DCS implemented the radio PTT functions the same in all of the aircraft so that we wouldn't have to turn on and off plugin settings to get these things to work correctly. (Or they could just build the Plugin functionality directly into the DCS product so that we don't have to use plugins. I've been spending the last week and countless hours trying to figure out why my Voice Attack+VIACOM Pro PTT Radio settings work in my A10C but don't work in my F/A-18.
  21. I tried this tonight, unmapped the hat switch on the throttle to see if that fixed it and it made it worse in that when I pushed the mic switch to one of the PTT positions the radio in the cockpit didn't respond and tune into a channel. When I mapped it back the radio did respond in that I could see it tuning to the correct channel. If I said "Options" I could get the Comms menu to appear and issue commands. The thing that I want to try to do is to get the Comms menu to show up as soon as I push the PTT hat switch and with out having to say "Options" This whole thing though still doesn't work as well as how it works in the A10C. All of this stuff works perfectly for me over there.
  22. Thanks but I checked that already. I have that option in Viamcom pro disabled because I actually want to see the menus.
  23. Interesting... Do you have any experience with the A10C? IF so would you say that the radio and comms menu mapping is different between the two planes? I have it working as desired in the A10C and tried to do the same thing in the F/A-18 and its not working. Tonight I will try un-mapping the MIC switch in DCS. You say I should map them in VIACOM PRO only, maybe that is my problem. The question I have is where would I do that? Do you mean map it in Voice Attack? Thanks for your input here. This is really helpful.
  24. OMG... its like there is a "sim with in the sim" for "flying" the CBUs. Very helpful... thanks. My next question would be does anyone share the feeling that I have that the CBUs never end up doing all that much damage to the targets? I dropped four of them in a ripple onto the compounds in the A10C "Hideout" and "Serpents Head" missions.. I think each drop took out one or two ground targets at the most. I expected it to be more effective. Maybe the secret is that you have to adjust the CBU settings to optimize the dispersal patterns? Sean
  25. Hi, Does anyone know how the dipersal pattern for ripples with CBUs works? Lets say you ripple three CBUs with a spread pattern of 75'. Does that mean that they will be 75' apart in a line that's parallel with the fall line? Or perpendicular to the fall line? Or a combination of both? Also, if you ripple 3 bombs do you need to hold down the button for the ripple program to release all three or do you just push the button and all three go automatically?
×
×
  • Create New...