[NO BUG] Major problems in 'Training' missions

[BattleAxes Skinner]

1. After exiting the 'training' missions, the axis controls assigned get messed up. Specifially, the 'Roll' and the 'Rudder' controls get a 'Red' highlight - which basically means that these controls have been rendered ineffective.
   

 

1. The RIO training missions are a complete and utter mess. After hitting the 'spacebar' to switch to the RIO seat, the RIO cockpit view is not loaded-up properly. Cannot follow the training at all after this. It's totally useless.
   

 

I don't understand how can a developer launch a 'new' module without properly testing the 'Training' missions?!?!? And that too when it's the most expensive 'module' yet. Jesus!

Edited April 13, 2019 by IronMike

[Cobra847]

1. 
   After exiting the 'training' missions, the axis controls assigned get messed up. Specifially, the 'Roll' and the 'Rudder' controls get a 'Red' highlight - which basically means that these controls have been rendered ineffective.
   

 

Not an F-14 bug. Not sure why your axes are being reassigned.

 

The RIO training missions are a complete and utter mess. After hitting the 'spacebar' to switch to the RIO seat, the RIO cockpit view is not loaded-up properly. Cannot follow the training at all after this. It's totally useless.

 

Unpause the sim so that the LoD changes. You can pause it once the RIO panels appear.

Not really a bug. Engine limitation.

[BattleAxes Skinner]

Well, the only axis controls that get messed up are for the F14 and not of any other module. If not an F14 bug then why does this happen?

 

Not quite sure what you mean by 'Unpause' the sim. The sim is not 'paused' in the first place!

[fl0w]

I don't understand how can a developer launch a 'new' module without properly testing the 'Training' missions?!?!? And that too when it's the most expensive 'module' yet. Jesus!

 

I know right! It's almost as if there are other 3rd parties that do this as well, and seemingly have these bugs that they never could've found! :huh: I wonder why...

[Cobra847]

I know right! It's almost as if there are other 3rd parties that do this as well, and seemingly have these bugs that they never could've found! :huh: I wonder why...

 

The two bugs in this thread do not seem to be reproducible atm.

Edited March 21, 2019 by Cobra847

[Cobra847]

Well, the only axis controls that get messed up are for the F14 and not of any other module. If not an F14 bug then why does this happen?

 

Not quite sure what you mean by 'Unpause' the sim. The sim is not 'paused' in the first place!

 

Try the mission again please, and ensure you don't pause the sim before switching seats.

 

I don't know why your axis assignments are conflicted, but it's extremely unlikely to be caused by a training mission.

[BattleAxes Skinner]

Try the mission again please, and ensure you don't pause the sim before switching seats.

 

 

 

I don't know why your axis assignments are conflicted, but it's extremely unlikely to be caused by a training mission.

 

 

 

Believe me Cobra, I have tried this multiple times. The mission asks the trainee to hit ‘spacebar’ to ‘continue’ the training and not to ‘pause’ the training. Upon hitting the ‘spacebar’, the view shifts from the front cockpit to the rear cockpit, and it just doesn’t load properly. It’s as if the RIO is having an out-of-body experience. Plz at least try this once yourself. You’ll know what am talking about.

 

Also, the F14 axis assignments seem to only mess up after one exits after doing any of the F14 training missions >> shuts down DCS >> and restarts DCS. Again, plz try it for yourself. I am reporting this after having done this over and over and over again.

 

 

Sent from my iPhone using Tapatalk

[IronMike]

All modules are affected by the input bug, this issue has been reported before the Tomcat release and occured with other modules as well. Why and when it happens is random. And it does not happen to everybody.

 

Our apologies for your inconveniences, but it is likely a coincidence that this happens with the training mission. Most players got rid of it by deleting their inputs and redoing them, if I may kindly suggest you try that. If this is a first time occurance, I would strongly recommend it. After this usually players do not get it again with the same module.

 

Please let us know how it went.

[IronMike]

Believe me Cobra, I have tried this multiple times. The mission asks the trainee to hit ‘spacebar’ to ‘continue’ the training and not to ‘pause’ the training. Upon hitting the ‘spacebar’, the view shifts from the front cockpit to the rear cockpit, and it just doesn’t load properly. It’s as if the RIO is having an out-of-body experience. Plz at least try this once yourself. You’ll know what am talking about.

 

Also, the F14 axis assignments seem to only mess up after one exits after doing any of the F14 training missions >> shuts down DCS >> and restarts DCS. Again, plz try it for yourself. I am reporting this after having done this over and over and over again.

 

 

Sent from my iPhone using Tapatalk

 

 

 

 

Do you press only spacebar, or do you switch to the RIO seat by pressing something else?

 

EDIT: I just retested all RIO training missions and none of the above occured, switching back and continueing was almost instanteneous for me, and the controls stayed untouched.

[BattleAxes Skinner]

Do you press only spacebar, or do you switch to the RIO seat by pressing something else?

 

EDIT: I just retested all RIO training missions and none of the above occured, switching back and continueing was almost instanteneous for me, and the controls stayed untouched.

 

 

 

I only press ‘spacebar’ Alex. Nothing else.

 

 

Sent from my iPhone using Tapatalk

[IronMike]

I only press ‘spacebar’ Alex. Nothing else.

 

 

Sent from my iPhone using Tapatalk

 

 

 

 

Ok, I think we found the issue, our instructions are not clear enough. In order to switch to the RIO seat, you need to press "2" on the keyboard. (2 for RIO, 1 for Pilot by default.) We will change the instruction to make this more clear.

 

However this might help us narrow down at least one reason why the inputs break, as the training mission utilizes highlighting of RIO input controls, which if not switched back properly might affect your pilot inputs, as you, as the player, are techincally still occupying the pilot seat.

 

Please try again by pressing 2 before pressing the spacebar to continue, it should now work as intended.

 

Thank you for bringing this to our attention, it is a small detail, but I can see how it can lead to confusion.

 

S!

[BattleAxes Skinner]

All modules are affected by the input bug, this issue has been reported before the Tomcat release and occured with other modules as well. Why and when it happens is random. And it does not happen to everybody.

 

Our apologies for your inconveniences, but it is likely a coincidence that this happens with the training mission. Most players got rid of it by deleting their inputs and redoing them, if I may kindly suggest you try that. If this is a first time occurance, I would strongly recommend it. After this usually players do not get it again with the same module.

 

Please let us know how it went.

 

 

 

Thanks Alex. I have been deleting the ‘F14B’ sub-folder within the ‘Input’ folder to get rid of the ‘red’ highlight. Is this what you meant? If yes, then I have been repeatedly doing it, but the problem keeps recurring.

 

 

Sent from my iPhone using Tapatalk

[BattleAxes Skinner]

Ok, I think we found the issue, our instructions are not clear enough. In order to switch to the RIO seat, you need to press "2" on the keyboard. (2 for RIO, 1 for Pilot by default.) We will change the instruction to make this more clear.

 

However this might help us narrow down at least one reason why the inputs break, as the training mission utilizes highlighting of RIO input controls, which if not switched back properly might affect your pilot inputs, as you, as the player, are techincally still occupying the pilot seat.

 

Please try again by pressing 2 before pressing the spacebar to continue, it should now work as intended.

 

Thank you for bringing this to our attention, it is a small detail, but I can see how it can lead to confusion.

 

S!

 

Thanks Alex.

 

Pressing 2 worked. Could do the RIO 'training' missions now.

 

However, the input error still persists :(

[Krustysan]

Works fine when using 1 & 2 to swap seats, but the instructions are vague - if you haven't swapped seats before hitting "space" to continue the mission, then you switch to RIO, the body remains, and no more swapping. The tutorial forces a RIO seat view, even if you haven't used "2" to get there.

 

A note in the tutorial instructions to hit "2" and then "space" should clear it right up. I know this seems like idiot-proofing, but it's the tutorial.

 

(Off topic: when it's quiet, the switch and small motor sounds are just great - attention to detail makes it feel real.)