kingfish

Hi all, VAICOM asked me to update this morning for new features, so I did. I also completed the "Finish" steps as requested. However, the console is now filled with a constant stream of: 9:16:31.433 there was a problem sending state update request:'VoiceAttack.VoiceAttackInvokeProxyClass' does not contain a definition for 'Dictation'Microsoft.CSharp.RuntimeBinder.RuntimeBinderException: 'VoiceAttack.VoiceAttackInvokeProxyClass' does not contain a d... The error message is very long, and there's a new one every few seconds. If I try to use VAICOM, it throws a different error: 9:21:46.563 UNABLE TO INVOKE PLUGIN, 'VAICOM PRO 2.5'. DUE TO EXCEPTION: 'VoiceAttack.VoiceAttackInvokeProxyClass' does not contain a definition for 'Dictation' I am running VA as admin, and I have tried resetting Keywords from the Reset tab in case something had gotten messed up. Neither of these things has worked. Any suggestions?

VAICOM has been updated to work pretty well with Supercarrier. You can do all of the required comms for proper landing procedure, and you can order the deck crew around for launch. I highly recommend it, not only for the added immersion, but freeing up your hands from having to navigate the comms menu in flight is really helpful.

This just happened to me on the latest OB. I was in the Mav F training mission on Caucasus. I fired all four Mavs at the targets, then I tried to do some A2G gun passes on the remaining targets. I noticed all my bullets were hitting well high, even though the pipper was dead on and I had an "in range" cue. I thought this was weird so I quit and did some googling. After finding this thread I was going to go back and record a track, but it appears to be working just fine now... I will keep trying to figure out the conditions that made this happen.

You're not the only one! I've been doing some test launches on the PG map. Usable video from the DL pod at <35nm. Still a signal out to about 60nm (can see the crosshairs, barely), but its so fuzzy/snowy that its unusable. I've gotten the issue both with the missiles/target in my forward quarter and in my aft quarter with A ANT selected. Not sure if this is an issue in procedure, an issue in ED implementation, or just how SLAMs work. Edit: I should clarify that I tried this at ~15kft and about 30kft, same result.

This is possibly a "Just dont worry about it" issue: VAICOM generally works fine for me (normal stuff, AIRIO, and carrier ATC), but when I hit "test" in the editor panel, it shows a bunch of missing aliases followed by "377 missing aliases in VA profile VAICOM PRO for DCS World." I've tried repeating the FINISH steps again to see if that would help, but it doesn't change anything. Have I messed something up, or should I just not worry about it as long as everything seems to be functioning?

I am also having this issue on a Valve Index. Have not tried this yet.

I have an index. I'm still working on upgrading my cpu to better run dcs in VR, but even on my ancient vishera processor at 20 fps, it's pretty amazing. I can read dials and ddis in the hornet no problem. Xplane 11 is also excellent in terms of visibility and immersion. I don't have anything else to compare to aside from trackir, which VR obviously beats the snot out of in coolness.

Its an old thread, but I have the same issue. Link: https://imgur.com/a/EOJdMUH

I've had a few similar issues with the triggers for the missions. As a temporary workaround, I've found that pressing and holding the prompted button for an extra second rather than just clicking works much better at getting detected.

This is very interesting. Do you know what year/block/etc that your manual is for? It may be that this feature was only added to later models, or to Polish exports, or something like that. If its supposedly on all of the bis models, then this would be a great feature to have.

Looks great! Would it be possible to get a version of this that uses primarily feet/nautical miles/knots/lbm/lbf as they are the units in the F-86 instruments?

Yeah, it looks super dirty cause I've been filing and sanding it. However, even when it was brand new and super clean I had the same issue. Yeah, I cut out that whole middle structure because the connector cable didn't fit, and removing the plastic seemed easier than trimming down the connector cable to fit. After some fiddling I believe I can get away with fitting a spacer down into the threads so that the plastic insert bottoms out and presses the insert onto the stick base and holds everything in place.

I'm not sure what you mean by "depressions in the inner ring" exactly. Can you clarify? Also, here's what I got. Its gotten pretty banged up, but it still threads into the other parts of the hose connector just fine. The threads on the right are filed down, as the major diameter was ~20-25 thou more than the connector on the WH base. However, it still does not fit, as it appears the minor diameter of the threads is too large as well, and that's a lot harder to fix.

I have already removed the center plug, as my connector cable was too big to fit. The issue is not something prevent the threads from reaching each other, but that the threads are different sizes and don't quite go together unless I literally wrench it down.

Hey all, I'm making my own warthog extension. Per the suggestion of you fine folks on this forum and those over at /r/hoggit, I bought a gardena hose connector. However, while the female part of the hose connector fits onto the base of the stick just fine, the inner plastic male part only threads into the Warthog stick about 3/4 of a turn before becoming too tight to turn any further. however, this is not far enough in to make a secure connection, so the stick itself can wobble because there is nothing keeping the nut rigid with the stick. Upon measuring the threads, it appears the gardena hose connector is ~20 thou bigger, which explains why it doesn't thread. Nobody else seems to be having any issues though. Whats the solution? edit: This is the connector