Hillman

Yes, good idea. I will try that. Thanks for the support!

Ok, that I did not know. Thanks for the tip - I will try it. No, I only use DCS on this machine, but could try IL2 or some other. I upgraded to v2 in hope of solving this, but no. I also asked on the Discord, but the opinion was that it was a problem with DCS. Not sure exactly when this problem started... I used VA for a long time without any issues earlier. Might be when I switched to Pimax Crystal VR, but unsure...

>Oh, you're using VA for the radio? No, I guess I was a bit unclear. I have a separate button as a VoiceAttack PTT button. I typically use VA for things like "Cockpit" (F1), "External" (F2), "Salute" (??), "Escape" (Esc) etc. As I'm using a motion rig I can't use a keyboard easily. I have a trackball fixed to the rig which works well. So for radio I'm stuck with the menues using the trackball (or voice saying "F-one" etc). The key-bond trick is nice, something I will try as well if I can find some free buttons somewhere I was actually using Vaicom before it was made open-source, but gave it up because it did no work well with the modules I used. I'm planning to start using it again once I get VA it self to work consistently. Unfortunately many times the VA PTT keypress don't register until several seconds later, which is very anoying. I have tried to run as Admin, setting High CPU priority, used different buttons etc.

I have been using Vaicom previously, but that was on an older PC. So now there should be no ref to Vaicom. I have never had problems with VoiceAttack before this campaign and I don't see why it should interfere in any way. I do however see that VA gets delayed by DCS from time to time. When I press the PTT button it seems do be qued somewhere before VA react. Happens 2-3% of the time. Very strange and a bit frustrating.

After getting orders to RTB, you are asked to switch to marshall on PRI. The usuall graphic/message about using F10/Spacabar/R/I to confirm only says F10 and remains after switching channel and pressing space. Looks like the new nice logic with joystick bind does not work in this mission. This also seem to mess up the Kiss-off logic. Another thing. I my first try Pshyco dived into the ocean after laying out the smoke. I used voice attack (but no mods) so I tried again without and she did not crash this time. First time I have had an issue with VA in any campaigns. A bit unfortunate as VA is nearly mandatory for me in VR and motion rig.

In the kneeboard the callsigns are given as Raven 1. Should be Springfield 7.

A minor detail question on the briefing: In the screenshot it says EVT 1 LAU: 8000 REC: 09:00 CASE 1 Should it be 08:00 instead of 8000? Looking forward to get started on the legendary campaign!

Yes, I double-checked this creating a simple mission with a 2-plan flight and asking my wingman to "go to tanker". If I then call the tanker I will get the starboard hose. If I call the tanker first and then ask wingman to hit the tanker, I will get the port hose. Played around a bit on this and pretty sure this is how it works.

I had the same probelm in M13: Impossible to refuel on the right hose. No problem on the left. I seem to remember plugging on the right in M8. In M13 I arrived after Lead already had finnished. I wonder if that is the problem... (If left is not in use, then right is not working? Something to test...)

Ah. I see what I did wrong. I pushed the swithes 1-4 forward, not to the B position! Never used ext power before and did not read the instructions properly. Learn something new every day.

Seems like it has nothing to do with the campaign. Tested in one of the Instant action and it's the same there. Maybe something has changed in DCS or I'm missing something.

Hi, I think I followed the instructions (ask for ground power, switch on battery, ext. power reset (which springs back to mid pos) and then swithces P1-P4), but the radio won't turn on and the alignment wont start. Most instruments work, but not the radio. Only when I start the R engine can I progress. Am I missing something herre?

I had no issues until I was sent to intercept the enemy. The callouts from the Awcs said the altitude was 15.000, but in reality he was at 1.000 feet. The bullseye references was correct though. He was extremely fast and I ran out of gass before I could hit the tanker after being called off the chase... Apart from this issue with the altitude callouts the mission seems to be fine.

Hi, A question not strictly related to the campaign, but anyway: When locating the enemy the JTAC says something like "3.5 miles to the north of <known point>"; How du I judge 3.5 miles when operating the TPOD? Thanks for a great campaign!

I have the DOF H3 rig and confirm I have the same problem entering the catapult shuttle. Clearly there must be something off here and I don't understand why not ED can look into this without having a motion rig available. I would assume the telemetry is possible to capture without? Anyway I have managed to reduce the oscilations by tuning up the "Smoothing Effects" on the "Sway" effect/axis in SRS (the software for the rig). Of course this then reduce other cases for this effect, but at least I can launch now.