[1.8+] DebugStuff - (2020-06-29) See the hidden secrets of the game objects

[linuxgurugamer]

20 minutes ago, alexus said:

Debug button does not work. v1.4.5

Ummm, worked for me.  I just installed the version posted a few messages up.

What button are you talking about?  This mod doesn't have a button, it is activated by typing alt-P

Edited September 6, 2018 by linuxgurugamer

[Electrocutor]

The download link in the OP is outdated.

[Jacke]

8 hours ago, Electrocutor said:

The download link in the OP is outdated.

As @linuxgurugamer pointed out in the post right above yours, the mod still works in KSP 1.4.5.  And the download still works.  What more is needed?

Edited September 27, 2018 by Jacke

[HebaruSan]

@sarbian, would you mind if we indexed this in CKAN?

[sarbian]

3 hours ago, HebaruSan said:

@sarbian, would you mind if we indexed this in CKAN?

Feel free to do it.

[HebaruSan]

36 minutes ago, sarbian said:

Feel free to do it.

Any game version compatibility limitations you'd like us to apply? From the forum thread title it looks like it's KSP 1.0 and later?

[sarbian]

There is not much ksp specific in it so 1.0+ should do

[cyberKerb]

Hi @sarbian, Firstly - thanks again for a useful tool - it's quite handy when working out what's going on in the game.

Had a question - Under the Module: ModuleWheelBase there is a 'radius' setting for... ummm.. something. When changing this value in the wheel part cfg file, I can see its effect on the wheel by how far the wheel model is above the ground or sunken into the ground.

However, I can't see this object that this radius setting controls in the debugstuff tool. Is this something that could be visible using this tool? Or is the problem that this isn't an object that I'm changing the radius?
For reference, Below images are of a wheel set to a radius of 0.2, 0.4 & 0.1. I've cycled through the PART and OBJECT options down to level 90 looking at both bounds and colliders and I don't see anything on screen that scales with the radius setting.

Radius=0.2 (For reference - This is close to the correct radius setting for the wheel - about 0.24)

Radius=0.4 ('something' is now too large and results in a floating wheel)

Radius=0.1 ('something' is now too small and results in a wheel clipping into the ground)

Edited February 28, 2019 by wile1411

[sarbian]

7 hours ago, wile1411 said:

However, I can't see this object that this radius setting controls in the debugstuff tool. Is this something that could be visible using this tool? Or is the problem that this isn't an object that I'm changing the radius?

It is not an object. I could display it as a cylinder or a circle but it is not related to a mesh or a collider (AFAIK)

[cyberKerb]

3 hours ago, sarbian said:

It is not an object. I could display it as a cylinder or a circle but it is not related to a mesh or a collider (AFAIK)

Thanks Sarbian. It would be great if it could be visible. I had the impression it was a collider, but that was only based on the wording of the ModuleWheelBase settings that I was playing with. Do you know what the correct terminology I should use for it? Also, for my understanding, do you know if the settings are adjusting something that is part of the model or is it something that the game add at runtime?

[Ruedii]

Cool!  Should be stock! 

Is there any way you could move this to insert this into the Stock Debug panel? 

[HafCoJoe]

15 hours ago, Ruedii said:

Cool!  Should be stock! 

Is there any way you could move this to insert this into the Stock Debug panel? 

Ohh that would be awesome... I could play stock again if that happened!

[cakepie]

Edit: added supported for WheelCollider, PR submitted

 

----- Original post -----

On 2/28/2019 at 1:34 PM, wile1411 said:

 do you know if the settings are adjusting something that is part of the model or is it something that the game add at runtime?

Somewhat late but @wile1411 looks like you are referring to config fields such as these from RoveMax Model M1 (roverWheel1)

	MODULE
	{
		name = ModuleWheelBase
		
		wheelColliderTransformName = WheelCollider		
		wheelTransformName = WheelPivot
		
		wheelType = MOTORIZED

		// setting this to true will override the radius and center parameters
		FitWheelColliderToMesh = False		
		radius = 0.378
		center = 0,0,0
		mass = 0.040
		groundHeightOffset = 0
				
		// ..
	}

Those values for radius, center, etc are for vehicle physics, e.g. position the part accordingly with wheel center at radius above terrain mesh. It doesn't involve any visual part of the model (i.e. meshes) nor use any "traditional" collider (e.g. one of the primitive colliders or a MeshCollider -- though a collider is still needed in your model if you don't want kerbals walking right through the wheel, just won't be used for vehicle physics.) I believe this is using a WheelCollider. The flag FitWheelColliderToMesh looks like it provides a mechanism to derive the radius/center values automatically from the model mesh (and thus, as the comment suggests, will override values in the cfg.)

However it is not strictly correct to say that the WheelCollider is not an object -- it is in fact part of the GameObject hierarchy that DebugStuff pulls out and dumps, second from bottom for roverWheel1:

[DebugStuff]
+roverWheel1 T:Untagged L:0 (Default)
|   Transform - roverWheel1
|   Part - roverWheel1
|   Highlighter - roverWheel1
|   // blah blah blah
|   AudioSource - roverWheel1
|   Rigidbody - roverWheel1
| 
 --+model T:Untagged L:0 (Default)
   |   Transform - model
   | 
   |--+roverWheel1 T:Untagged L:0 (Default)
   |  |   Transform - roverWheel1
   |  | 
   |  ( // a whole lot of stuff )
   |                   
   |---WheelCollider T:Untagged L:0 (Default)
   |      Transform - WheelCollider
   |      WheelCollider - WheelCollider
   |    
    ---Surface Attach Collider T:Untagged L:0 (Default)
          Transform - Surface Attach Collider
          SphereCollider - Surface Attach Collider

 

But it isn't one of those that DebugStuff shows when drawing colliders.

 

 

 

 

Edited April 26, 2019 by cakepie
fix PR'ed

[sarbian]

I somehow missed all those PR...

Anyway, the PR are merged and a build for KSP 1.8 is out : DebugStuff-1.6.0.0.zip

Edited October 18, 2019 by sarbian

[sarbian]

And I forgot to change the used shader, which made the drawing 100% less visible. So here is a fix

DebugStuff-1.6.1.0.zip

[flart]

1.6.0.0 and 1.6.1.0 aren't compatible for <1.8.0. Could you add limitation to the CKAN?

UPD. @HebaruSan

Edited November 1, 2019 by flart

[sarbian]

New 1.7 version with a few new features and improvements by @DMagic : Better UI visualization, joint support, Animation info, variant support and other stuff I may have missed.

Download : DebugStuff-1.7.0.0.zip