Greyman

I am just giving the Anton a try, via the 2-day free trial, and have been going through the training missions. When on the final training mission, the one on bombing, I cannot get any of the bombs to drop. I have checked the forum and found a few threads on this, so I have double checked that I have all of the settings right. That includes making sure that the top circuit breaker in the front fuse box, has not mysteriously been switched off and making sure that i am pressing the same button on my WH joystick that i have mapped to bomb release. the bombing and fusing mode selector is set as per the instructions and the amber light is lit. There are bombs visible, under the aircraft by the way. I must be missing something, but if I am, it might be a good idea for the training mission to point that out.

Its 2-day free trial starts tomorrow, so maybe just give it a try. That's what I'll be doing

Thanks @Bankler. I know it might seem that i was implicating your mission and that wasn't my intention. I make great use of the mission and I thought that this thread would be the most likely place to find someone who had experienced something similar. As you suggest, I've not experienced it since, so it does look like it's a rare one. Thanks again, for your help and for creating this excellent mission.

https://forums.eagle.ru/showpost.php?p=3670706&postcount=3 Might help

Please post a video of when you do :)

If it isn't there, just create it. Notepad should do the trick.

+1 for the realistic approach. Easycomms, or a form of it, could be used by peeps who don't want to be manually tuning the radio at busy times. I use VAICOM, in VR, and that will hopefully remove the need for comms menu navigation via the keyboard.

Slartibartfast might be available, although it might be a bit of a challenge getting him from Magrathea with all of these travel bans in place :)

I'm sure that the Grim Reapers, with the help of some WWII warbirds, will do their best to decrease that level of comfort. :)

A bit of a noob question i know, but I've just returned to the Hornet after a bit of a break and managed to catch the 3-wire, after a few tries. However, in return, it caught me. It just wouldn't let go, despite me raising and lowering the hook and throttling up and down. I only managed to get free by taxiing all the way to the stern of the flight deck. Is there an easy way to either free oneself from such a situation or, perhaps better still, to avoid getting into it in the first place?

Didn't DID do a more detailed version of EF2000 for the RAF to help train pilots?

..or go to the UI layer of the control settings and map either or both of the two zoom options. They are instant, hold-down-the-key, zooms, rather than axis zooms, but do the job.

Did you try it out first and then buy it? If so, you would need to uninstall the trial copy before installing the bought one.

I'd check that the snapped cable was not the only one that was damaged and that you remake any broken connections correctly. It might also be possible that connections could be broken during the reassembly of the stick, so take care when doing that. Good luck with getting it working again.

maybe check that your anti-virus software hasn't quarantined the file.

The VAICOM Pro thread does contain posts and advice about exactly your setup, so that you should be able to find the way to successfully use VAICOM Pro (with its AIRIO addon), SRS and the F14B module.

Interesting: as the dump file contained the words "ACCESS VIOLATION", i guessed that running DCS as administrator might solve the problem and whether it was doing so that solved it or something else, i managed to get through the mission. Maybe give it a try

yup, the 3rd bunker going pop, or the subsequent AI assault on the village might well have been the trigger for my CTD too.

After destroying the 2 sandboxes and 1 bunker and sometimes a MANPAD infantryman, when i call in the wingman to engage ground targets, at a variable amount of time afterwards, i get the CTD message that asks me if i want to send the crash information. This has now happened about 4 times and although i might be able to get past it by not calling the wingman in, that shouldn't be necessary. EDIT: It would appear that it is not related to the use of the comms menu as it still crashes without using it. Never mind. It looks like it has already been reported, albeit not sorted yet.

You didn't accidentally calibrate it or reset the calibration via the windows tool did you?

I'm seeing the off-centred ball also, so if the flight model hasn't been changed, could it be an initial aircraft trim setting, possibly not even designed for choppers and/or that has no mapping to be synchronised with controllers, that has been inadvertently set up oddly?

Maybe check out the "realistic TDC slew" option on the Special tab of the settings. IIRC, having that checked means that you need to hold the button depressed while you move the slew stick around and this was unreliable with at least the WH HOTAS. Having the check box cleared, makes the TDC depress act as it does in the A10c, so slew the box over the target and then depress the TDC to lock. This may be the same for your HOTAS and the update may have set the option to on.

They should ideally build in some "machine learning", so that when the leader tells them they are "an incompetent fool", or equivalent, for not obeying an order, they try much harder next time. :)

If we are talking about the two mirrors that you can see through the ceiling of the cockpit, I saw my 3 wingmen in them today, during a mission in the Deployment Campaign, so they do appear to be working as they should. By the way, the Mirrors checkbox is on the Gameplay tab in settings, accessed via the "cog" on the home screen.

LOL, get in there :)