Project

General

Profile

Bug #13188

F12 Aerodynamic Overlay Crash to Desktop Bug

Added by Anth12 over 7 years ago. Updated over 7 years ago.

Status:
Closed
Severity:
High
Assignee:
-
Category:
Gameplay
Target version:
Start date:
11/04/2016
% Done:

100%

Version:
Platform:
Linux, OSX, Windows
Expansion:
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

GOG KSP 1.2.0.1586 64bit Clean Install. No Mods: Sandbox
GOG KSP 1.2.1.1604 64bit Clean Install. No Mods: Sandbox

After watching a part of EJ_SA twitch stream, there was mention of a bug relating to the Aerodynamic Overlay crashing KSP to desktop

Testing in 1.2.0.1586, there is no problem

The Crash only happens in 1.2.1.1604 when I do the following:

1. Select a ship as long as it has some wing surface. Launch from SPH or VAH
2. Press F12 to turn on aerodynamic overlay
3. Press F12 again to turn off aerodynamic overlay
4. Move the mouse pointer over the wing surface.

Wing Surface can be flaps, canards, wings.

Hope that helps. I couldnt find another bug report on this.

-.txt (81.5 KB) -.txt OSX crash JPLRepo, 11/04/2016 10:58 AM
error.log (37.7 KB) error.log Windows crash JPLRepo, 11/04/2016 10:59 AM
output_log.txt (474 KB) output_log.txt Windows crash JPLRepo, 11/04/2016 10:59 AM
2016-11-04_144110.zip (72.6 KB) 2016-11-04_144110.zip [email protected] zel_knight, 11/04/2016 07:46 PM
2016-11-04_152140.zip (75.4 KB) 2016-11-04_152140.zip [email protected] zel_knight, 11/04/2016 07:46 PM

Related issues

Related to Kerbal Space Program - Bug #13232: Random crashes during ship flight/operations x64 (access violation)Duplicate11/14/2016

Related to Kerbal Space Program - Bug #13236: Crash mousing over craft in atmo flight Duplicate11/15/2016

History

#1 Updated by rudi1291 over 7 years ago

  • Status changed from New to Confirmed
  • % Done changed from 0 to 10

Tested on both 32bit and 64bit, does happen on both. Only happens if "Highlight FX" and "Part Highlighter active in flight" are on (in the graphics settings)

#2 Updated by Anth12 over 7 years ago

Nice picking up the graphics settings being a factor.

To give more information:
If "Highlight FX" is off and "Part Highlighter active in flight" is on the bug doesnt happen
If "Highlight FX" is on and "Part Highlighter active in flight" is off the bug doesnt happen
If "Highlight FX" is off and "Part Highlighter active in flight" is off the bug doesnt happen

It only happens if both are set to on at the same time.

#4 Updated by sal_vager over 7 years ago

In my testing here you don't even need a wing, this occurs with a Mk1 pod alone.

#5 Updated by sal_vager over 7 years ago

  • Severity changed from Normal to High
  • Platform Linux added

Rating as high as this does break the game for all players (not a local issue).

#6 Updated by JPLRepo over 7 years ago

Confirmed also under OSX and Windows.

#7 Updated by JPLRepo over 7 years ago

#8 Updated by Anth12 over 7 years ago

I tested it with the Aeris 4A (stock) which has the Mk1 cockpit which doesnt crash when the mouse pointer goes over it.

and then tested it with the GDLV3 (stock) which doesnt have any pods or cockpits, which didnt crash with any part that the pointer moved over until i added wings to it.

Just assumed it was wing related after that. My bad

#9 Updated by JPLRepo over 7 years ago

  • Platform OSX added

#10 Updated by zel_knight over 7 years ago

Adding my error logs as I believe this also describes the CTD I've experienced just recently. KSP 1.2.1 Win x64 no mods.

#11 Updated by sal_vager over 7 years ago

  • Related to Bug #13232: Random crashes during ship flight/operations x64 (access violation) added

#12 Updated by sal_vager over 7 years ago

  • Related to Bug #13236: Crash mousing over craft in atmo flight added

#13 Updated by JPLRepo over 7 years ago

  • Status changed from Confirmed to Ready to Test
  • Target version set to 1.2.2
  • % Done changed from 10 to 80

This should be fixed in 1.2.2. Please test.

#14 Updated by Anth12 over 7 years ago

  • Status changed from Ready to Test to Resolved
  • % Done changed from 80 to 100

Resolved it is.

#15 Updated by JPLRepo over 7 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF