Sandman1330

Anyone? Or do I have to submit an official support ticket for all these questions?

I've made a recent post, I'm new to VAICOM but I'm finding that Jester very frequently acknowledges my order, but doesn't do it. Tuning TACANs is the big one I've noticed - he'll roger the request, but not make any changes.

Good day, Just got VAICOM - struggling through the setup but making progress. I bought it mostly to control Jester in the F14. Question: If a mission has more than one Texaco (Say, Texaco 1-1, Texaco 2-1, etc), can I have Jester tune 2-1? It seems right now the commands only exist for Arco, Shell and Texaco, with no provision for additional flights. Thx Edit (many edits as I add questions along the way): Further questions: 1. How do I get Jester to "tune tac" for a radio frequency? I can't find a command, and it would take longer to look up the frequency and read it out to him than it would just to use the wheel to "tune tac"; 2. How do I get Jester to "tune tac" for the new Supercarrier TACAN? It doesn't show up in the list. Same as above, manual tuning defeats the purpose; 3. My question above, what about when there are more than one Texaco? 4. Is there any way to get the Jester wheel back for times when my spoken message just isn't getting through? 5. I am getting no response oftentimes from valid commands. Jester responds affirmative when I tell him to tune the Stennis TACAN, but he doesn't actually do it - or worse, he puts in the wrong frequency! I notice this with tankers especially - I say "tacan tune arco" and he tunes up Shell! Or "tacan tune shell" and I get Arco! 6. Realistic ATC - Doing a Case III, the readback from the player of the marshall instructions is wrong, commence time comes up as 00 every time and I think the DME was wrong too. It seems the entire comms has been shortened, is there a way to disable this and stick with the default DCS calls? 7. SRS integration - I have set it up per the manual, but I am still not clear about what steps to take in cockpit. If I want to make an SRS call, what do I do differently than if I want to make a VAICOM command? 8. Calling for "Status" or "interrogate" activates triggers within my mission. Those triggers are usually done as additional items from the F10 menu (spawning AI fighters). The triggers are all vanilla editor, done by turning flags on/off via F10 menu. 9. Even when having Jester manually tune a tanker frequency, as soon as I request rejoin ("approaching for refuel"), the frequency changes automatically to the frequency of one of the OTHER tankers, not the one I want to use! "Select tunes radio" and "instant select" are unchecked in settings, easy comms in mission on or off makes no difference.

I’ve had the blackout on launch issue occasionally as well. Though I haven’t extensively tested, my initial impression is it seems to happen more when the aircraft is heavy (6PH loadout or lots of bombs). I’ll see if I can do a track today if I can reproduce it, but I’ve had bad luck with tracks lately...

The F14 module already has this, it’s super cool!

Yeah, same. Probably because I find a tendency to float in close, so I have to reduce power a smidge just before the ramp, otherwise I go from centered ball to high ball / bolter. Alternately I’ve been able to hold 1-2 dots low on ball, then without touching throttle I’ve been able to get _OK_ 4 wires, though I don’t like this solution. In both cases I go full burner as soon as I hit the deck. In my mission I have 30kts down the angle (15kts ship speed, 15kts wind 18* left of BRC), so I don’t think island burble or anything like that are a factor. It almost feels like a ground effect...

I have been getting this in Rift S as well. I thought my HMD was dying!

In the latest open beta, I’m having a similar issue. I need to do some more testing, but after a couple hours of multiplayer, I start to get terrible stutters and high frametimes, even though the in game FPS counter remains around 40. I believe it may be related to the supercarrier, as it happens most around the new boat. Using afterburner to monitor the system, it seems my memory gets pegged at 28-30GB usage for DCS alone (I have 32GB). Further, eventually I start getting low disk space errors, which leads me to believe windows is increasing the page file size to compensate for the maxed out RAM. GPU is my limiting factor (it’s always maxed at 99-100), but when frame time spikes, there is a corresponding drop in GPU usage, indicating a bottleneck somewhere else - RAM, methinks. Perhaps the new SC has a memory leak issue? Graphics settings:

Yes, they are there in the server log - but they are incorrect! I run my own server (sitting beside my gaming system and connected via KVM switch). I just did a pass that showed up as an _OK_ in game, but I was in such disbelief I switched to the server and pulled up the log to verify. In the log, with the correct date and timestamp for the pass I just did, it showed --- and a bunch of errors that didn't show up in game. I'm not sure which grade was more correct (it felt like a good pass), but the grade shown in game and the one saved to the log are not consistent with each other.

Seriously? I have trouble believing this isn't giving everybody trouble, I thought it would see more traction. Any decent number of escort ships and this becomes a major issue - I can't call the carrier 50 miles out like I'm supposed to... Sometimes I can't even get it from right on top!

Cool, thx! Here’s hoping they fix the long standing issue of getting RWR Launch and track indications from other flights far away from ownship, otherwise pullback will be constantly overriding our currently selected mode, even if the threat is far away and isn’t directed at you...

Is SP mode supposed to automatically select the highest threat? Right now it doesn’t. I have found myself many times locked and fired upon unexpectedly and having to spam the seq/raid/fov to try and quickly box the threat radar system in order to engage. And then I usually end up overshooting it and having to cycle all the way back around again, ha. One would think it should automatically switch in SP mode?

Well said.

You guys really are pushing the envelope on what is possible within the DCS environment - you’ve done amazing work with this module and things like this are bound to happen!

You can see it, you just can’t spawn on it or catch a wire.

Forgive my stupid question, but you have purchased and installed the supercarrier module, correct? If you haven’t both purchased and installed via the module manager, you can’t catch any wires on the new SC. (I think that’s the one you are using in the photo?) I’ve seen a few guys who have forgotten to install it and had this problem.

:thumbup:

MSAA is very GPU intensive. Just a shot in the dark as I haven’t tried this myself yet, but is it possible your bottleneck is not the GPU, but maybe CPU, or RAM, or somewhere else? If you have the GPU horsepower, the MSAA shouldn’t lower FPS much until the GPU is maxed out. For OP, with a 9700K and 1080, it’s possible or maybe probable that you are GPU limited, so potentially there is an issue. Can you use Afterburner or another program to verify if your GPU is running near 100%?

Already acknowledged by Heatblur, they’re working on it.

I noticed it too! Took a screenshot to post it but you beat me to it. It does appear in some real life photos, but it must be collapsible as a seahawk is much larger than a Huey and would certainly have clearance issues.

Worked! Mostly. Once the tanker runs out of fuel and RTBs, the new spawn reverts back to the default Texaco 1-1 callsign. Should the assigned callsign persist upon respawn?

:doh: Thanks. Thought it had to be something simple. I can assume this will also apply to all other customizations, such as TACAN frequency and orbit locations / altitudes?

Thanks! I'm new to MOOSE, but I've got the recovery tanker working. However, I can't seem to get the callsign to change. Here is the script I am using: The S3B takes off as it should, and sets itself up in the pattern. However, I cannot for the life of me get the callsign change command to work. I've tried variations per the MOOSE help file (TexacoStennis:SetCallsign(2) for example), but nothing. Am I missing something?

I think it’s because the wings are starting in emergency oversweep mode (a good thing, as it prevents spawn in collisions and is realistic) Place the emergency sweep handle forward, push it down and close the guard, then hit master reset. The CADC error should clear and auto mode will work. I had no problems once I did this procedure yesterday. PS: 1000th post!

If you have the ball call bound to a key, you can call it anytime, even if it’s not available in the comm menu. I’ve accidentally called the ball while sitting on the deck. Then the LSO came back with “you’re a little low...” :megalol: