phiol

I was wondering if it was possible to keep the @tex_map 1 when using jit.gl.material.

In this example I am using jit.gl.text , but I also like to know because I cannot maintain

the @tex_map 1 with jit.gl.model and .dae files.

I was wondering if it was possible to keep the @tex_map 1 when using jit.gl.material.
In this example I am using jit.gl.text , but I also like to know because I cannot maintain
the @tex_map 1 with jit.gl.model and .dae files. 

maintain-tex_map-1-when-using-jit-gl-material

Hi Raja , thanks for the tip , I check it out.

But I believe my problem remains jit.gl.material not having a @tex_map 1 because i'm actually using jit.gl.mesh and not jit.gl.model.

Here below (patch) you can see the problem. As mentioned , I'm using jit.gl.mesh with the @tex_map 1

But maybe you trick would work and I wouldn't have to put @tex_map 1 in the 1st place ?

Hi Raja , thanks for the tip , I check it out.
But I believe my problem remains jit.gl.material not having a @tex_map 1 because i'm actually using jit.gl.mesh and not jit.gl.model. 

Here below (patch) you can see the problem. As mentioned , I'm using jit.gl.mesh with the @tex_map 1 

But maybe you trick would work and I wouldn't have to put @tex_map 1 in the 1st place ? 

it's supposed to look like your 1st pict. But I would like to add the nice "phong" shininess of jit.gl.material.

Hook up the jit.gl.material and see what happens.

it's supposed to look like your 1st pict. But I would like to add the nice "phong" shininess of jit.gl.material.
Hook up the jit.gl.material and see what happens.


@tex_map uses the fixed function opengl shading pipeline, and this is not compatible with the programable shader pipeline enabled via jit.gl.material. if you want @tex_map functionality with shaders, you will have to create your own shader that emulates this functionality.

searching the googs for something like "emulate gltexgen shader" should give you some info.

hi phiol.
@tex_map uses the fixed function opengl shading pipeline, and this is not compatible with the programable shader pipeline enabled via jit.gl.material. if you want @tex_map functionality with shaders, you will have to create your own shader that emulates this functionality.

searching the googs for something like "emulate gltexgen shader" should give you some info.


So I 'll the answer as a NO IT 'S NOT DOABLE for now.

Would , exporting my own models from blender in the manner that Raja suggested , help solve this ??

I found this on the googs
So I 'll the answer as a NO IT 'S NOT DOABLE for now. 

Would , exporting my own models from blender in the manner that Raja suggested , help solve this ?? 

(i doubt it, i was way off with that. sorry. exporting models from blender in the manner i suggested merely allows you to keep the texture exported from blender, but probably still wouldn't allow you to use jit.gl.material to modify it(would still be a texture created by a fixed pipeline once exported?)... but who knows, i haven't actually tried, and i'm sure to be wrong of many things as i'm just starting out here... and i'm also not a very smart person, just look at my username)

quite honestly, pure glsl code (out of glpix) is clearly above my competence at the present. So I ‘ll the answer as a NO IT ‘S NOT DOABLE for now.

i won't argue with that, because i understand the 'for now' part of that statement VERY WELL :D

but just for the sake of the longer-term(it'd be nice to be able to search these forums and find more examples of the advanced math involved in working with computer generated graphics, rather than being dependent on just the visual/object-interface part of max which is partly designed for quicker results, not necessarily thorough ones), see the attachment here, it's just an exercise i tried... and succeeded :) (without any experience in openGL/GLSL whatsoever before this...)

most importantly visit the linked source page(live-coding tutorials, start with the simple 'palm tree'... it'll make you feel like this crap is less daunting i promise ;D).

it might not show you the exact tex_map functions you want, but it really helped me understand textures/fragment-shaders/GLSL-like-code in general in a more immediately useable way(as well as how to go between the code and the visual-object interface of max).

'for now' is a good thing :) but comfort never lasts. (Phiol, you're much more advanced than me at all of this, so i's jus thinkin, maybe if ya keep searching you'll find things that help it make better sense to you, and that would in turn help many here who follow what you do.... just sayin: over the long run. not in any immediate/pressured way, just give it a shot, over and over, while not worrying about it :)

(...and sorry if i interrupted the thread a bit)

i won't argue with that, because i understand the 'for now' part of that statement VERY WELL :D
but just for the sake of the longer-term(it'd be nice to be able to search these forums and find more examples of the advanced math involved in working with computer generated graphics, rather than being dependent on just the visual/object-interface part of max which is partly designed for quicker results, not necessarily thorough ones), see the attachment here, it's just an exercise i tried... and succeeded :) (without any experience in openGL/GLSL whatsoever before this...)
most importantly visit the linked source page(live-coding tutorials, start with the simple 'palm tree'... it'll make you feel like this crap is less daunting i promise ;D).
it might not show you the exact tex_map functions you want, but it really helped me understand textures/fragment-shaders/GLSL-like-code in general in a more immediately useable way(as well as how to go between the code and the visual-object interface of max).
'for now' is a good thing :) but comfort never lasts. (Phiol, you're much more advanced than me at all of this, so i's jus thinkin, maybe if ya keep searching you'll find things that help it make better sense to you, and that would in turn help many here who follow what you do.... just sayin: over the long run. not in any immediate/pressured way, just give it a shot, over and over, while not worrying about it :)

(...and sorry if i interrupted the thread a bit)


Great answer Raja , I 'll take a look @ your patch later today.

>>(Phiol, you’re much more advanced than me at all of this, so i’s jus thinkin, maybe if ya keep searching you’ll find things that help it make better sense to you, and that would in turn help many here who follow what you do…. just sayin: over the long run. not in any immediate/pressured way, just give it a shot, over and over, while not worrying about it :)

-Thanks, And that's exactly what I've been doing literally every single day for the past 15 months. (except for 2 weeks in june last year, Where I took a trip to the west coast for the 1st time and actually made it out to cycling 74's head quarters @ 730 Clementina Street, San Francisco, CA 94103, Only to find out that is had turned into a body-board /surf or something shop. Haa! Later that day I found out it was now 340 S. Lemon Avenue #4074 Walnut, CA 91789. SO I made it to L.A. but never to cycling74.

As you can see, even making it to C74 was not straight forward ;-)

Great answer Raja , I 'll take a look @ your patch later today.
>>(Phiol, you’re much more advanced than me at all of this, so i’s jus thinkin, maybe if ya keep searching you’ll find things that help it make better sense to you, and that would in turn help many here who follow what you do…. just sayin: over the long run. not in any immediate/pressured way, just give it a shot, over and over, while not worrying about it :)

-Thanks, And that's exactly what I've been doing literally every single day for the past 15 months. (except for 2 weeks in june last year, Where I took a trip to the west coast for the 1st time and actually made it out to cycling 74's head quarters @ 730 Clementina Street, San Francisco, CA 94103,  Only to find out that is had turned into a body-board /surf or something shop. Haa! Later that day I found out it was now 340 S. Lemon Avenue #4074 Walnut, CA 91789. SO I made it to L.A. but never to cycling74. 

As you can see, even making it to C74  was not straight forward  ;-)
phiol


Raja !! that patch is insane man ! Wow great work, thank for sharing.

 and couldn't find the code you claim you translated to jit.gl.pix from Iñigo Quílez's live coding session of 'an eye ball':

Raja !! that patch is insane man ! Wow great work, thank for sharing.
I quickly looked @ the http://www.iquilezles.org/ and couldn't find the code you claim you translated to jit.gl.pix from Iñigo Quílez's live coding session of 'an eye ball':

couldn’t find the code you claim you translated to jit.gl.pix from Iñigo Quílez’s live coding session of ‘an eye ball'

oh, thought i left it in there, but maybe not:

(it's the youtube vids on that page... the simple palm tree looking one is where i started, it's titled 'the principles of painting with maths' )

the code is in the video(so i took the video to offliberty.com, and downloaded it to my comp, so it's easier to view and repeat.... although, watching them on youtube 0.5 speed-time-stretch is also kinda nice))

oh, thought i left it in there, but maybe not:
http://www.iquilezles.org/live/index.htm
(it's the youtube vids on that page... the simple palm tree looking one is where i started, it's titled 'the principles of painting with maths' )
the code is in the video(so i took the video to offliberty.com, and downloaded it to my comp, so it's easier to view and repeat.... although, watching them on youtube 0.5 speed-time-stretch is also kinda nice))

maintain @tex_map 1 when using jit.gl.material