Brian

I've created a fairly large project using Jitter OpenGL, which relies heavily on transparency. Whenever I try to export the patch as an application, however, all transparency is broken. It works in the patch, just not in the app. This is a sci-viz project that visualizes ionosphere data, so I need to be able to see through the animation to the globe underneath. I've tried setting @depth_enable to 0 for all meshes. No good. I have a feeling this is getting into some pretty arcane (to me anyway) OpenGL stuff that is testing my admittedly limited knowledge of the subject. Any help would be appreciated. I could upload the patch, but it's fairly large and includes a lot of JS and some external data files. I'd like to see if there's just some OpenGL idiosyncrasy that I'm overlooking before posting it.

maintaining-opengl-geometry-transparency-on-app-export

Ok, so I've been banging my head against this for a while and it seems like the transparency is fine. So nix that. For some reason it seems the jit.movie object won't display the texture I've loaded in, so the geometry underneath just doesn't show up at all. The image is included in the search path and I've even put it in numerous package subfolders, but the standalone version just won't display it. It can find it (I tried omitting it to see if the app would complain and it did) It just won't display it for some reason. If I send the plain old "read" message and open the image from elsewhere, everything's fine and dandy. Just can't get it to loadbang on startup. Anyone else experienced this?

I haven't tried this but if you're in max 7 you could try jit.movie @moviefile nameyourfile

Also, the equivalent of thispatcher in standalones is

I haven't tried this but if you're in max 7 you could try jit.movie @moviefile nameyourfile
Also, the equivalent of thispatcher in standalones is
;
sendapppath r_name

I am running Max 7 so thanks for the heads up about the @moviefile attribute. I'll give both suggestions a try. If all else fails, I'll replicate the error in a smaller patch and post it here.

Thanks for the response.
I am running Max 7 so thanks for the heads up about the @moviefile attribute. I'll give both suggestions a try. If all else fails, I'll replicate the error in a smaller patch and post it here.


Thanks PHIOL for the sendapppath suggestion. It helped reveal what the problem is. Even though I have the "Make application subfolder" and the "search for missing files" options both checked in the inspector for the [standalone] object, Jitter objects in the app are still only looking for user files in the top level—wherever the app itself happens to be, whether on the desktop or in a folder. Once the sendapppath message spat out that location, I put the image there, et voila: it worked fine. What's weird is I have [fpic] objects calling other png files I've included and they show up fine. It's just the jitter objects that do this. Maybe you or someone else knows why? I've included a sample patch that replicates the problem. Obviously, you'll need your own images:

Success! (sort of).
Thanks PHIOL for the sendapppath suggestion. It helped reveal what the problem is. Even though I have the "Make application subfolder" and the "search for missing files" options both checked in the inspector for the [standalone] object, Jitter objects in the app are still only looking for user files in the top level—wherever the app itself happens to be, whether on the desktop or in a folder. Once the sendapppath message spat out that location, I put the image there, et voila: it worked fine. What's weird is I have [fpic] objects calling other png files I've included and they show up fine. It's just the jitter objects that do this. Maybe you or someone else knows why? I've included a sample patch that replicates the problem. Obviously, you'll need your own images:

Maintaining OpenGL Geometry Transparency on App Export