Compiled with Python version 2.5.4.
Checking for installed Python... got it!
Traceback (most recent call last):
File "/Applications/Blender 2.49/blender.app/Contents/MacOS/.blender/scripts/stk_browser.py", line 566, in Draw
tmp_but = Draw.Number("", self.NextButton(), x, y, 100, textheight, int(current_value), 0, 100000000)
ValueError: invalid literal for int() with base 10: ''
Auria {l Wrote}:See attached screenshot; I tried it on Canyon track and I get a lot of parameter errors
EDIT: also note that "arena" is neither yes nor no; I suppose "no" should be checked. Same for fog
Auria {l Wrote}:Also, I believe many sky-* properties are only appropriate for sky domes so if you wish to make something really neat they could be hidden if you select another sky type
Also, we have the need to support plain-color skies, so I suppose this should be another option
My first piority is getting it to work right. After that we could have a look at improvements.
asciimonster {l Wrote}:P.S. Wouldn't it be better to have the modellers determine where the start positions are just like the collectibles now (empty objects with type "start") the in stead of the game engine that take the, somewhat cumbersome, start-* properties?
hiker {l Wrote}:*grin* I've said that for ages, till too many people complained that this is just too much work (e.g. to define the 20 correct start positions).
hiker {l Wrote}:Sorry for not participating actively here, too busy
asciimonster {l Wrote}:Could somebody explain what properties are assigned to end camera's?
I can't seem to understand the explanation on this page
This is as far as I came:
- type = ignore -> Don't use as end cam
- type = "" -> Use as end cam (but that is not the behaviour I have seen)
- type = "ahead" -> Seems to be the default now
- type = "fixed" -> What's the difference with a single end camera?
- start = ??? -> I have no idea what type this property should be...
I think it's easier to set type="endcamera" to use it as an end cam rather than type being empty. Then a second property "endcamtype" defines it's behaviour.
P.S. Are particle-emitters and billboards attached to objects, and if so which ones?
hiker {l Wrote}:Could you perhaps try to improve the docs (once you understand what I meant)?
asciimonster {l Wrote}:hiker {l Wrote}:Could you perhaps try to improve the docs (once you understand what I meant)?
Will do.
hiker {l Wrote}:This is a general property for all objects: anything with type=ignore will be ignored, so that's not camera specific.
Hmm . Just this line forces me to rethink parts of the Property Browser. I was under the assumption that all objects only have one "type"; now I see that every object has a Blender "type" and a STK "type", which are dependent on eachother.:
hiker {l Wrote}:asciimonster {l Wrote}:hiker {l Wrote}:Could you perhaps try to improve the docs (once you understand what I meant)?
Will do.
asciimonster {l Wrote}:P.S. How many of you are using the stk browser? And if so, do you find it useful?
Auria {l Wrote}:* in "sky", "dome" is selected by default (when you create a new track), but the parameters under it, like sky-texture, don't appear until you click "box" then click back on "dome"
Auria {l Wrote}:* if you're already scrolled to the top and you press "up" one more time, the next click on "down" has no effect
Auria {l Wrote}:Also, I might add that the "Use Current" button is not very clear? Maybe a tooltip could be displayed when you hover the button
Auria {l Wrote}:Otherwise, very nice work, don't give up
Auria {l Wrote}:Maybe you could add this to the materials setup editor?
Auria {l Wrote}:we have "alpha", "transparency", "additive". Those 3 are exclusive. So I suggest to create something like "graphical-effects", with all those items (plus "No transparency" or so) on a single line and you can select only one item.
lSTK_Picklist = {
"graphical-effect": "none|water|smoke",\
+ "texture-effect": "none|alpha|transparency|additive",\
lPropertyDef = {
+ "texture-effect":[type_PICKLIST,"none"],\
- "additive":[type_BOOLEAN,"no"],\
- "transparency":[type_BOOLEAN,"no"],\
- "alpha":[type_BOOLEAN,"no"],\
lSTKTypes2Properties = {
+- "Texture":["clampU","clampV","texture-effect","light","sphere","slowdown-time","anisotropic",\
Users browsing this forum: No registered users and 1 guest