[0.22] UbioZur Welding Ltd. 2.0 Dev STOPPED

Redchrome · January 12, 2015

Ok could you please enable the advanced Debugging for the welding and then weld a part and send us the log of that.
There are some Points:
You are the second who said that the camera after at launch would move to strange position and rotation, which has nothing directly to do with the welding but maybe the parts.
Welding happens inside the editor and it creates a new part, to use this new part, you need to enable the database reload in the welding settings, or restart the game, welded parts do by default not appear in the running season of the game.
Regulary the editor should be cleaned after the welding process, that is why I ask you for a log with the advanced debug option.

Sorry about the slow response to this, I was away all weekend.

I have a few more notes from my last attempt (before I got your message about turning on debugging):

* I have restarted the game several times, since I'd read the cautions about not all mods like being reloaded in the middle of the game. The parts I welded still do not appear in the list of available parts.

* One time, I tried welding my part, the welding GUI wouldn't close after clicking the weld button, so I exited the VAB (ended up 'beside' it again), clicked on it again to re-enter, tried picking a Huge HexCan (from EPL) and the part appeared halfway buried in the 'floor' of the VAB. This makes me suspect that something is messing up the coordinate system within the game.

* I tried welding a couple of metal cans (from EPL), and did get the GUI to give me some options, then close. When re-loading the craft, only 1 part (out of the two claimed to be there) was visible!

* I tried putting that 'craft' on the launch pad, and got an error message about 'craft size unknown'

* Now I can't get the craft 'Load' GUI to appear in the VAB or SPH! So my game is broken until I sort that out. I'm going to try removing the broken craft files and see if that fixes things.

I'm doing this on OSX with the standard iMac keyboard, and the OS is hijacking the function keys, so I can't use all of them. Not all of them seem to remap as easily as others. I'm still sorting out how to get access to the function-key functionality, but I haven't looked at it hard. I will try to find time today to get my game working again and see if I can debug some of this for you.

- - - Updated - - -

@Redchrome By the way, do you, by chance, have no Kerbal Konstructs installed?

I do not know what Kerbal Konstructs is, I do not have it installed.

I will post my list of installed mods when I start debugging this more assiduously.

girka2k · January 12, 2015

@Redchrome

As far as I can tell, you are the first known user of this mod who uses OSX! For this mod it is not surprising that it doesn't work on your system!

There already were problems on Linux, we were able to correct them. Most likely, we will be able to help you too, but first you will need to provide logs - I don't know how some things works in OSX version of KSP.

Edited January 12, 2015 by girka2k
typo

mendahu · January 12, 2015

@girka2k I used the strut method for another cool thing, too.

http://i.imgur.com/a0lNNl3.gif

It's a sun shade made out of Procedural Fairings. It has a nested docking washer/free-moving washer to make two doors working in tandem.

Procedural Fairings and IR are my favourite mods (after Welder, of course!).

Redchrome · January 12, 2015

I tried to do a simple test of welding a couple of parts together and taking detailed notes and screenshots. However, everything worked pretty much as I would expect it to, without any glaring bugs.

So I don't yet have a detailed example of things breaking. On the upside, I have a useful baseline of comparison for when things work as expected. For the record, below is a listing of what I did and the results I got.

If you'd like, PM me and I'll send you the screenshots and my KSP.log.

Now to try more things and see what breaks and when. I wouldn't be surprised if my earlier problems were due to some quirk of the parts I was using.

Started a new game named welding_debug, Sandbox mode, Easy Difficulty

Upon loading, I got the welcome message from Gene Kerman (and chose "Thanks, I've got it"),
and the EPL dialog with the default options "Always use resources" and "Allow progressive builds" set (and chose "OK").

Opened the debug menu by pressing Option+F12 (previously having changed my keyboard settings using the advice here: http://forum.kerbalspaceprogram.com/threads/31391-Opening-debug-console-on-a-Mac since I'm doing this on OSX).
Noted that this took a screenshot at the same time, but I think this is a feature of Steam since it didn't go into the usual KSP screenshots directory.

Clicked on VAB
With no ship loaded, tried clicking the Welding button to see if I could bring up a settings configuration. No result.

Load menu works (it stopped working in my other sandbox game after I tried experimenting with welding)

Starting with nothing, I chose an FL-T100 tank which became my root part in the expected position.
Choosing another FL-T100 I connected it on top of the first tank.

Clicking on the Welding button, I now get a GUI with a 'Settings' button.
Took screenshot
Set 'Advanced Debug' and 'Database Autoreload' from the Settings menu
Took screenshot
Saved settings
Took screenshot

Chose the 'Weld it' button.
Gave it a name.
took a screenshot
Got the welding progress dialog, and lots of data scrolled by on the debug menu. Processed for a long time, then gave a dialog saying "New part saved and shipped!"
Clicked 'Ok'
New part now available in the Fuel Tanks menu.
I even found a part I'd welded before, but thought didn't work.

Exited VAB
Camera view was normal

Quit the game
Saved KSP.log

- - - Updated - - -

Ok, I have what appears to be a repeat of the bug I experienced before. Here's my testing methodology and screenshots of the result. PM me and I'll send you my KSP.log file.

Loaded saved game welding_debug, Sandbox mode, Easy DifficultyOpened the debug menu and set it to show the debug log.
clicked on VAB


Starting with nothing, chose an MSV-2000 metal can from EPL.
I note that this can, when the module was first installed on my system, used to appear in the Utility menu.
Now it is only visible on the Metal resource type on the Advanced part selection menu.


Verified welding Advanced Debug was turned on


Chose a second MSV-2000 can and put it atop the first one.


Chose the 'Weld it' button. 
Got no progress on the welding GUI.
debug log showed "-- End Welding -- | 2 parts welded"
debug log showed "[Exception] IndexOutOfRangeException Array Index is out of range"
The part cannot be moved around the VAB.
GUI does not go away.
took a screenshot
[img=http://i292.photobucket.com/albums/mm12/redchrome/KSP%20Welding%20debug/screenshot15.png]

Exited VAB
Found that the camera view was from beside the VAB, facing the SPH.
took screenshot
[img=http://i292.photobucket.com/albums/mm12/redchrome/KSP%20Welding%20debug/screenshot16.png]


quit the game
saved KSP.log

- - - Updated - - -

Further testing, as before, PM me for the KSP.log of this debugging session.

Loaded saved game welding_debug, Sandbox mode, Easy Difficulty
clicked on VAB


Starting with nothing, chose an MSV-2000 metal can from EPL.
As before, I note that this can, when the module was first installed on my system, used to appear in the Utility menu.
Now it is only visible on the Metal resource type on the Advanced part selection menu.




Choose two Rockomax Brand Adapters and put them on either end of the container, inverting the lower one so the whole assembly is tapered
 at each end.
Attached a Clamp-O-Tron docking port to each end, inverting the lower one so that it is usable.


Realized I'd forgotten the debug menu. Opened the debug menu and set it to show the debug log.


Verified welding Advanced debug is turned on


Chose the 'Weld it' button.
As before, GUI froze, exception appeared in log.
Took screenshot
[img=http://i292.photobucket.com/albums/mm12/redchrome/KSP%20Welding%20debug/screenshot17.png]


Exited VAB
As before, view after exiting VAB was facing the SPH rather than the conventional higher view.
Upon re-entering the VAB, I noted that only the root part of the craft I had worked on, was visible.
Also that the name was "VesselName" instead of "Untitled Space Craft".
Also that the part-picker sidebar was unusable.
Took screenshot.
[img=http://i292.photobucket.com/albums/mm12/redchrome/KSP%20Welding%20debug/screenshot18.png]


Exited VAB
Took screenshot of debug log as a reference for what was going on at this point in the log
[img=http://i292.photobucket.com/albums/mm12/redchrome/KSP%20Welding%20debug/screenshot25.png]


Clicked on VAB again
No vessed visible this time
Chose the Mk3 fuel tank long fuselage section.
Noted that the part appeared with one end of it on the 'floor' of the VAB instead of in midair. On one previous occasion I saw a part (a
 Large Rocket Parts can) buried halfway into the floor when it appeared. Perhaps the difference in whether the part appears on the floor
 or buried halfway into the floor is based on the origin of a coordinate system describing the part?
Took screenshot
[img=http://i292.photobucket.com/albums/mm12/redchrome/KSP%20Welding%20debug/screenshot27.png]


quit the game
saved KSP.log

Fax287 · January 13, 2015

Because UbioZur has kindly allowed to update his work, Girka2k and I have released the next update for this great mod.
Download
Latest changes:
Compatibility with KSP 0.90
Added Partselection
Fixed problems with Config laoding
Added <MaximizedModuleAttributes> for values where only the highest is wanted like the new SAS Level
Added <ModulesToMultiply> for Modules that shall be added mutliple times
Fixed problems with Modulemerging where sometimes modules would not be added correctly
2014-12-31 (ver2.1.0)
Compatibility with KSP 0.90
Added Partselection
Fixed problems with Config laoding
Added <MaximizedModuleAttributes> for values where only the highest is wanted like the new SAS Level
Added <ModulesToMultiply> for Modules that shall be added mutliple times
Fixed problems with Modulemerging where sometimes modules would not be added correctly
2014-12-03 (ver.05)
Fixed wrong rescaling of some models in KSP 0.25
Improved database reloading with ModuleManager installed
Updated <ModulesToIgnore> list
Dropped compatibility with KSP 0.24.
2014-11-01 (ver.04)
Fixed wrong rotation of models in some cases (especially in SHP)
Now topmost and lowest nodes are placed to the end of list for fix impossibility to attach welded part to other in VAB/SHP. (It is assumed that the topmost and lowest nodes, most likely, are stack nodes)
Most floating-point values (excluding amount of resources) of welded part are rounded to 5 fractional digits
Some other minor fixes
2014-10-21
KSP 0.25 compatibility
Stock Toolbar integration.
Added the GUI to change most settings.
Added ability for change requiredTech from GUI.
Improved naming of the partfiles - now welded part can be saved in file named like folder (for example "WeldedPod.cfg", not "part.cfg").
Tweakscale integration. Now it reads scale from scene part to include tweakscale.
Added the correct addition of entryCosts.
The ModuleAttributeList.xml gives you the ability to edit how the tool will process the merging of certain modules and their attributes. For details, see comments in the ModuleAttributeLists.xml file.

<Vector2CurveModules> section is the list of modules that have to be read as vector2 curves, as an example the ISP of an RCS thruster.
In <Vector4CurveModules> list are modules that will be read as vector4Curves that means they will create curves from floatpoints and tangents. There is a thread in the forum just about the magic of floatpoint tangents.
<SubModules> list contains the Submodules that otherwise would be ignored and not merged, Adding an entry here will give the tool the ability to merge the attributes in it.
Modules in <ModulesToIgnore> list will be completly ignored from the tool and not get added to the new part.
Entries in <AveragedModuleAttributes> will make sure that the tool will not simply add the values of this attribute from the different parts and modules up, but will calculate it as aritmetric mean (average).
Entries in <UnchangedModuleAttributes> list will give the tool the order to not merge the values for this attribute.
<BreakingModuleAttributes> might be the most important list of Attributes, the entries here will give the tool the order to check if the values of these attributes are equal, and only allow then the merging or the module, otherwise a new module would be added.
[*] Fixed crashTolerance, breakingForce and breakingTorque calculation. Improved MaxTemp calculation.
Now there is three methods of calculation crashTolerance, breakingForce and breakingTorque values:
legacy (UbioZur variant)
arithmetic mean value of the values of parts
weighted average by mass (now it's default)
[*] Also it presents new ways of calculation of MaxTemp:
arithmetic mean value of the values of parts (UbioZur variant)
weighted average by mass
lowest between values of parts (now it's default)
[*] Changed config file format (and name).
[*] Fixed miscalculation in case of resources which have not equal amount and maxAmount values.
2014-09-02
Fixes incorrect rescaling of parts, containing "scale" in MODEL description.
2014-09-01
Fixed incorrect calculation of COM offset.
2014-08-12
KSP 0.24 compatibility.
Changed massless parts processing behavior.
Sources
Please note that this version is incompatible with KSP 0.25!
The latest version for 0.25
The latest version for 0.24.2
Legal stuff:
This work based on Malkuth's update for UbioZur's original code.
https://i.creativecommons.org/l/by-nc-sa/4.0/88x31.png
We will open a new thread the moment we change from maintaining this tool to releasing our own tool for this mod.
Please note this is not an official release from UbioZur!!!
Thank you UbioZur for kind permission to continue your work!

Is there an update for the latest version of .90?

girka2k · January 13, 2015

I tried to do a simple test of welding a couple of parts together and taking detailed notes and screenshots. However, everything worked pretty much as I would expect it to, without any glaring bugs.
So I don't yet have a detailed example of things breaking. On the upside, I have a useful baseline of comparison for when things work as expected. For the record, below is a listing of what I did and the results I got.
If you'd like, PM me and I'll send you the screenshots and my KSP.log.
(skip)

Well, it's all fine, thanks for the detailed report, but exactly what I'm need for start is full KSP.log and/or Player.log :blush: .

KSP shows not all information in debug console. Moreover I badly need some data from log when EDITOR scene just loaded.

I am quite sure that problem is at least "/" OS path delimiter like as in Linux, not "\". Using info from the log I'll make little addition to code and will propose you to test new build.

- - - Updated - - -

(skip)
Latest changes:

Compatibility with KSP 0.90
(skip)
Is there an update for the latest version of .90?

Yes, that's it

Edited January 13, 2015 by girka2k

Alewx · January 13, 2015