Auria {l Wrote}:Basically at this point, two properties are needed for a material : one to say that a material has a water effect (this already exists); the other is to add a "height" property
hiker {l Wrote}:I've added support for weather settings to the track exporter. I also converted fog color from [0.0,1.0] to [0,255], before noticing that you already do this for sky-color. Now I am a bit confused I don't care where we do it, but it should be done in the same program
hiker {l Wrote}:I also added animated textures for water nodes (identical to animated textures in the normal track). But I think that this is not yet supported by the browser (or did I miss something)?
python
>>> from symbol import except_clause
Traceback (most recent call last):
File "stk_browser.py", line 704, in Draw
for (prop_name,prop_type,current_value) in data.GetProperties(cur_objname):
File "stk_browser.py", line 368, in GetProperties
for prop in lSTKTypes2Properties[cur_stktype]:
KeyError: 'Start'
asciimonster {l Wrote}:First off let me say, unequivocally, that the browser should supply the correct value. If it doesn't it's my problem to solve.
A guiding principle in the browser is that it doesn't change any property until it is... changed. Even more so: The properties that have not yet been changed from it's default value aren't even created. It works similar to XSD vs. XML. In the XSD a node is defined with a default value, but that doesn't mean it has to be present in the corresponding XML.
So my guess is that the value has been set with the old version of the browser (set to 0.0,0.0,1.0) and hasn't been changed since (which automatically changes it to 256,256,256 format)... If it has been changed and it's still in the 1.0,1.0,1.0 format this is a bug I need to squash.
Also just like XSD you can define types. Both fog-color and sky-color are defined as type_COLOUR, and therefore handled exactly the same.hiker {l Wrote}:I also added animated textures for water nodes (identical to animated textures in the normal track). But I think that this is not yet supported by the browser (or did I miss something)?
There is not supported and not supported. The datamodel of the browser isn't configured to allow water objects to be animated. It's a question of changing the proverbial XSD.
STKRudy85 {l Wrote}:I report maybe another bug which appear in type-selection-menu : when I select start python crash in blender and report :
- {l Code}: {l Select All Code}
Traceback (most recent call last):
File "stk_browser.py", line 704, in Draw
for (prop_name,prop_type,current_value) in data.GetProperties(cur_objname):
File "stk_browser.py", line 368, in GetProperties
for prop in lSTKTypes2Properties[cur_stktype]:
KeyError: 'Start'
Auria {l Wrote}:I have a bug report : sometimes "anisotropic" is checked (set to 'yes') but when I export the track, materials.xml does not include anisotropic="y"
EDIT: another bug : many zipper parameters are not exported, I customized all parameters but only "speed-gain" was exported
Auria {l Wrote}:EDIT: oh, and yet another -.- we have a property called "friction" that can optionally be set, it seems like the browser doesn't support it
Auria {l Wrote}:EDIT: one more, sorry when skid condition is set to "skid" only, condition is not exported at all
hiker {l Wrote}:A guiding principle in the browser is that it doesn't change any property until it is... changed. Even more so: The properties that have not yet been changed from it's default value aren't even created. It works similar to XSD vs. XML. In the XSD a node is defined with a default value, but that doesn't mean it has to be present in the corresponding XML.
Hmm - I am not sure if that might have some disadvantages in the future. E.g. what if we should decide to change a default (admittedly unlikely, but who knows). If we would then re-export an old track, those properties would still not being exported, but since in STK then a different default would apply, some tracks might look different. From that point of view it looks to me to be better to export all values. Or am I missing something?
hiker {l Wrote}:Would it be a lot of work to disable this (i.e. leave the code in so that we can use it if we need to), but for now keep on getting the minimal materials files back? It's just that esp. atm with a lot of development happening I found myself looking at the materials.xml file quite often.
Auria {l Wrote}:I have a bug report : sometimes "anisotropic" is checked (set to 'yes') but when I export the track, materials.xml does not include anisotropic="y"
EDIT: another bug : many zipper parameters are not exported, I customized all parameters byt only "speed-gain" was exported
EDIT: oh, and yet another -.- we have a property called "friction" that can optionnally be set, it seems like the browser doesn't support it
EDIT: one more, sorry when skid condition is set to "skid" only, condition is not exported at all
<sun fog="true" fog-color="3060 1530 0" fog-start="0" fog-end="50"/>
Auria {l Wrote}:See attached screenshot : the "sound effect" section and the sound-related parameters are not together, which is rather weird
Auria {l Wrote}:(...) and, a little feature request, do you think sub-parameters like SFX parameters could appear indented?
Auria {l Wrote}:oh, and also, graphical-effect="smoke" no more exists, it was superseded by "particles", so you can remove that option please
Auria {l Wrote}:the fog issue described above is still there in latest version, is this known?
Users browsing this forum: No registered users and 1 guest