HOTAS controls stop working 10 min into the mission

[bswift]

I even did an auto shutdown (WIN-END) and the plane shut off successfully. However, still no controls, and the after burners were still on, and the plane did NOT drop out of the sky.

 

This is after the november update.

 

F-18 is the plane.

[Flappie]

Do you have the dcs.log file for this session? We might learn what happened if you can attach it.

[bswift]

Here are the last 2. If memory serves I was only in the ME after exiting the mission so it should be close to the end.

 

I did run a whole bunch of missions first, and it was ok.

 

I'm using MOOSE, but not sure that could affect something like this... Code is up on a branch: https://github.com/brettswift/dcs-mission-mp-sunrise-scramble/tree/fix/bombers-should-bomb-stuff

 

 

Logs.zip

[Flappie]

Thank you. I can't find anything abnormal in your log.

I see you have a driving wheel connected to your computer. Are you aware the lastest open beta have introduced a conflict with those? Well maybe yours works alright because it seems it doesn't stop DCS like it does to others.

 

Sometimes, when my HOTAS controls don't answer anymore, it's because I've left the Windows Game Bar (Win+ G) in a dirty way., and I'm forced to do some "Alt+Tabing" to get focus back on DCS.

[bswift]

I have that windows game stuff turned off, but it is entirely possible that something did just take focus away from DCS. I'll post if this happens again, and confirm I have focus on the window.

 

My wheel is a Fanatec 911 GT3RS - I wasn't aware there was a conflict with wheels - i'm not sure how that could be the case. I sit in front of the wheel and I think one profile I use the wheel as a button box.

 

Is there a link to where the conflict is being tracked - so I know when it's fixed or if it affects my wheel ?

[Fri13]

Have you tried that when you are flying, open up settings and go to key bindings and just press few HOTAS buttons that are not working so that the view jumps to the proper position, then just get back to game and try using them?

[Flappie]

My wheel is a Fanatec 911 GT3RS - I wasn't aware there was a conflict with wheels - i'm not sure how that could be the case. I sit in front of the wheel and I think one profile I use the wheel as a button box.

 

Is there a link to where the conflict is being tracked - so I know when it's fixed or if it affects my wheel ?

Here's the sticky from ED.

And here's the open beta changelog page. Wait and see.

[bswift]

I just tested again and it is still an issue, even with a plane that spawns late into the mission.

 

Fri13 - I haven't done exactly what you said, but I did go into axis controls, and test the axis.. they all were responding. However, going back into the game I had no controls.

 

The mission I liked to (on the branch) above, still has this issue. I've tried a couple of times. It's ONLY when I get to the Arco tanker though, which is a little strange. There's a moose command that fires right then sending the B1 bombers to a different waypoint.

 

2020-11-16 03:19:06.730 INFO EDTERRAINGRAPHICS41: instancer factors has been changed. Update lod buffers.

2020-11-16 03:19:06.730 INFO EDTERRAINGRAPHICS41: distanceFactor = 1.000000

2020-11-16 03:19:06.730 INFO EDTERRAINGRAPHICS41: instancerDistanceFactor = 1.000000

2020-11-16 03:19:06.730 INFO EDTERRAINGRAPHICS41: forestDistanceFactor = 1.000000

2020-11-16 03:19:06.730 INFO EDTERRAINGRAPHICS41: forestDensity = 1.000000

2020-11-16 03:19:06.796 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 0 59 squares

2020-11-16 03:19:06.798 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 1 59 squares

2020-11-16 03:19:06.798 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 2 25 squares

2020-11-16 03:19:06.799 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 3 75 squares

2020-11-16 03:19:06.799 INFO EDTERRAINGRAPHICS41: surface5 gc() 4.751200 ms

2020-11-16 03:19:10.527 DEBUG Scripting: make: country: 2

2020-11-16 03:19:10.527 DEBUG Scripting: Phrases make : key = 3

2020-11-16 03:19:10.528 DEBUG Scripting: Phrases make : key = 4252

2020-11-16 03:19:30.720 DEBUG LuaGUI: ---onBdaShowF10()--- bValue , isOn(): true true

2020-11-16 03:19:30.738 INFO EDTERRAINGRAPHICS41: instancer factors has been changed. Update lod buffers.

2020-11-16 03:19:30.738 INFO EDTERRAINGRAPHICS41: distanceFactor = 0.700000

2020-11-16 03:19:30.738 INFO EDTERRAINGRAPHICS41: instancerDistanceFactor = 1.000000

2020-11-16 03:19:30.738 INFO EDTERRAINGRAPHICS41: forestDistanceFactor = 0.500000

2020-11-16 03:19:30.738 INFO EDTERRAINGRAPHICS41: forestDensity = 1.000000

2020-11-16 03:19:42.324 INFO SCRIPTING: 64( -1)/E: BASE00000.function(BSLOG Bombers being sent to pre-bombing orbit)

2020-11-16 03:19:46.733 INFO SCRIPTING: 113097( -1)/I: ATIS01606.function(ATIS Vaziani | State Stopped: Freq=144.000 MHz AM, Relay unit=Radio Relay Vaziani (alive=true))

2020-11-16 03:20:17.443 DEBUG Scripting: make: country: 2

2020-11-16 03:20:17.443 DEBUG Scripting: Phrases make : key = 5

2020-11-16 03:20:17.443 DEBUG Scripting: Phrases make : key = 4252

2020-11-16 03:20:47.503 INFO SCRIPTING: 113097( -1)/I: ATIS01606.function(ATIS Vaziani | State Stopped: Freq=144.000 MHz AM, Relay unit=Radio Relay Vaziani (alive=true))

2020-11-16 03:22:21.931 WARNING LOG: 1 duplicate message(s) skipped.

2020-11-16 03:22:21.931 DEBUG Scripting: make: country: 2

2020-11-16 03:22:21.931 DEBUG Scripting: Phrases make : key = 3

2020-11-16 03:22:21.931 DEBUG Scripting: Phrases make : key = 4256

2020-11-16 03:22:31.411 DEBUG Scripting: make: country: 2

2020-11-16 03:22:31.412 DEBUG Scripting: Phrases make : key = 3

2020-11-16 03:22:31.412 DEBUG Scripting: Phrases make : key = 4252

2020-11-16 03:22:48.980 INFO SCRIPTING: 113097( -1)/I: ATIS01606.function(ATIS Vaziani | State Stopped: Freq=144.000 MHz AM, Relay unit=Radio Relay Vaziani (alive=true))

2020-11-16 03:23:08.048 INFO Lua: Lua CPU usage: metric: average mission execution: 1.0960 %

 

 

I also have a late spawn plane. When I get in it, the HOTAS axis controls work - but after about 60 seconds or so they stop working.

 

It's probably my MOOSE code that is causing this, however, my opinion is that no MOOSE code should cause the mission to stop.

 

Anyways, This is the moose code in question:

 

 

The code here is a reference:

https://github.com/brettswift/dcs-mission-mp-sunrise-scramble/blob/355f37e0d815b52bc8900c151da7a4678d8382be/MP_Caucus_Anapa_Mission_Start.lua#L63-L77

[bswift]

FYI - to see it, if you get in the first plane on Blue in the client list, follow startup - -take off and fly to waypoint 2.. you will see this.

 

 

It's a bit of a long lonely flight.. but.. it's also kind of a nice sunrise :D

 

[Flappie]

I couldn't reproduce your issue.

 

Try disabling hot plug devices.

[bswift]

I removed the MOOSE code in question - and the problem disappeared. I was just running a BAI mission on the B1's.

 

I'll work on the BAI feature again soon - and try your hotplug suggestion if I see it in the new build. Thanks!

[Flappie]

I would have never guessed this could be caused by a script. I agree with you, a mission script shouldn't prevent you from using your peripherals. That is an odd one.

Thanks for your feedback. :thumbup: