 | | Re: Doing Patterns and Bitmaps in MLCad
|
|
(...) [snip] Urg. Why so wordy? Just do: 0 TEXTURE <position vector> <orientation matrix> <filename.type> [START <standard ldraw commands go here> 0 TEXTURE END] The <position vector> and <orientation matrix> parameters are identical to the (...) (24 years ago, 5-Sep-00, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| |
| | Re: Doing Patterns and Bitmaps in MLCad
|
|
"Steve Bliss" <steve.bliss@home.com> wrote in message news:oekarsonpfetb7s...4ax.com... (...) I tend to agree about putting it all in 2 separate commands. However, I don't think a position vector and orientation matrix are appropriate. A texture is (...) (24 years ago, 6-Sep-00, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| |
| | Texture mapping spec? (was Re: Doing Patterns and Bitmaps in MLCad)
|
|
(...) Sorry, Computing course at college showing through. (We were told try and specify EVERYTHING. Unfotunatly there is no concrete defintion of what EVREYTHING is.) (...) Agreed, but with the following questions? (Assuming simple rectangular (...) (24 years ago, 6-Sep-00, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| |
| | Re: Texture mapping spec? (was Re: Doing Patterns and Bitmaps in MLCad) [DAT]
|
|
(...) I second this ideia, and I would also like to add that extra directories never hurt backwards compatibility. I also have to say that you I would like to remember that we should try to follow the path of the more experienced, like the creators (...) (24 years ago, 6-Sep-00, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| |
| | Re: Doing Patterns and Bitmaps in MLCad
|
|
(...) You are right. My approach assumed to much and restricted too much. (...) Good point. (...) OK. (...) Right. But if START is required, then it might as well be omitted. My purpose in having an optional START was to allow TEXTUREs without the (...) (24 years ago, 6-Sep-00, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| |
| | Re: Texture mapping spec? (was Re: Doing Patterns and Bitmaps in MLCad)
|
|
(...) :) I know what you mean. (...) Hmm. There shouldn't be any need for 'nested' textures. Or is 'nested texturing' an area of texture-mapping that I don't know about? Steve (24 years ago, 6-Sep-00, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| |
| | Re: Texture mapping spec? (was Re: Doing Patterns and Bitmaps in MLCad) [DAT]
|
|
(...) I orgot the Texture filename, so: 0 TEXTURE <texture_filename> <vector1> <vector2> <vector3> [<vector4>] So, Resuming again: 0 SET TEXTURE_WRAP on 0 MATRIX TEXTURE 1 0 0 0 0 1 0 0 0 0 1 0 0 0 0 1 Load 0 TEXTURE my_texture1.png 0 0 0 1 1 1 3 16 (...) (24 years ago, 6-Sep-00, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| |
| | Re: Texture mapping spec? (was Re: Doing Patterns and Bitmaps in MLCad)
|
|
"Steve Bliss" <steve.bliss@home.com> wrote in message news:4gvcrs8kb1v5s0n...4ax.com... (...) cope (...) I can't think of any reason to "nest" textures. The only reasons I know of to draw multiple textures over one another are to produce different (...) (24 years ago, 6-Sep-00, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| |
| | Re: Texture mapping spec? (was Re: Doing Patterns and Bitmaps in MLCad)
|
|
(...) This is what I meant by nested textres.- sub-textures. (...) You are right, I was wrong. However a more complex texture could be built up from simpler ones.(I.E No top level texture The sub texture being made up from simpler 'bitmaps') - This (...) (24 years ago, 6-Sep-00, to lugnet.cad.mlcad, lugnet.cad.dev)
|
