pbourke's picture

Paul (@pbourke)

Compositions

1 year ago
1 year ago
1 year ago
pbourke's picture
Paul commented on Paul's Discussion, “works on one mac not another

Thanks for the consideration. The original is quite a complex composition, lots of subcompositions etc. But I have stripped it all down to the attached. If you connect the image directly to the make unlit shader node, it works. If the GLSL shader is used, it doesn't. There are two windows grabs, correct_macmini.png and incorrect_macbookpro.png. I do not expect you to debug the GLSL shader but I'm curious/concerned as to why it works on the Mac Mini and on lots of other Macs but not my MacBook Pro.

pbourke's picture
Paul commented on Magneson's Composition, “Vertical Slit Scan

Nice.

pbourke's picture
Paul commented on Paul's Discussion, “works on one mac not another

The composition involves texture mapping onto OBJ read objects and image mapping for the texture through a GLSL shader. On the MacMini all is perfect, on the MacBook Pro it looks like the texture mapping is getting messed up.

MacBook Pro: NVIDIA GeForce GT 750M 2 GB Intel Iris Pro 1536 MB

MacMini: Intel HD Graphics 4000 1536 MB

pbourke's picture
Paul posted a new Discussion, “works on one mac not another

works on one mac not another

First let me acknowledge that this is not a clear/precise question, rather I'm fishing for ideas.

Here's what I have ... I developed a composition originally on a MacBook Pro. Then did some work on it on a Mac Mini. Probably went back and forward a bit, projects shared on the two machines via Dropbox (I always make sure it is up-to-date).

Now, it works on the MacMini but on the MacBook Pro it "runs" (no errors) but the results are clearly different, and unexpected.

pbourke's picture
Paul commented on Paul's Discussion, “List of XY from data

Thanks for that. Actually the bit I was missing was that one can use the first items in the file columns as a label in Get Table Columns.

Pages