Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gemvertexbuffer-help updated for attributes #72

Merged
merged 5 commits into from Sep 22, 2014
Merged

Conversation

jptrkz
Copy link
Contributor

@jptrkz jptrkz commented Sep 20, 2014

No description provided.

@umlaeute umlaeute merged commit da6a760 into umlaeute:master Sep 22, 2014
@umlaeute
Copy link
Owner

thanks for the help-patch.

do you have a screenshot of the expected result (the lower left quad is always empty for me)

@jptrkz
Copy link
Contributor Author

jptrkz commented Sep 22, 2014

screen shot 2014-09-22 at 10 49 40 am

@umlaeute
Copy link
Owner

hmm, my result differs:

glslattributes

i had to fix a number of things in your code to get the correct glsl program-id (just adding 0.5 is the wrong way to do it), and to prevent crashes. i also moved your example from the help-file into examples/10.glsl/16.vertexbuffer_attributes.pd.

could you please try an updated version of Gem (2c4a280) to see whether i accidentally broke something?

@umlaeute
Copy link
Owner

and this is what i get on OSX-10.9

glslattrib_osx

@jptrkz
Copy link
Contributor Author

jptrkz commented Sep 23, 2014

i tried earlier today with the latest gemvertex cpp/h and Gem src but got these errors:

In file included from gemvertexbuffer.cpp:17:
gemvertexbuffer.h:135: error: ‘gem::utils’ has not been declared
gemvertexbuffer.h:135: error: ISO C++ forbids declaration of ‘GLuintMap’ with no type
gemvertexbuffer.h:135: error: expected ‘;’ before ‘m_idmapper’
gemvertexbuffer.cpp: In constructor ‘gemvertexbuffer::gemvertexbuffer(t_floatarg)’:
gemvertexbuffer.cpp:163: error: class ‘gemvertexbuffer’ does not have any field named ‘m_idmapper’
gemvertexbuffer.cpp: In member function ‘void gemvertexbuffer::setProgramID(float)’:
gemvertexbuffer.cpp:626: error: ‘m_idmapper’ was not declared in this scope
gemvertexbuffer.cpp:627: error: expected type-specifier before ‘GemException’
gemvertexbuffer.cpp:627: error: expected )' before ‘&’ token gemvertexbuffer.cpp:627: error: expected{' before ‘&’ token
gemvertexbuffer.cpp:627: error: ‘x’ was not declared in this scope
gemvertexbuffer.cpp:627: error: expected `;' before ‘)’ token
make: *** [gemvertexbuffer.o] Error 1

@jptrkz
Copy link
Contributor Author

jptrkz commented Sep 23, 2014

"no need to run autogen.sh again.
though i really wonder how you managed to build before.
were you using the Xcode-project (which is not recommended, before you
start doing that)?"

you mean to get it up and running to begin with? no x-code. just a makefile with paths to gem-0.93.3 src

@jptrkz
Copy link
Contributor Author

jptrkz commented Sep 23, 2014

no luck with autogen.sh after gettext install (brew and manually from site with latest version)
still get "configure.ac: not using Gettext"

so the problems we're experiencing are probably rooted in the fact that i modded the files while using 0.93.3?

any other options to make the darwin (gem)?

@jptrkz
Copy link
Contributor Author

jptrkz commented Sep 26, 2014

ok finally got through ftgl/freetype swamp with the aid of this:
#28

edit
** i've compiled the latest Gem commit w/ pd-0.45-4 ** - i run the help patch and shader output is perfect - i can confirm it's the one you've made changes to because of the different output with a "print_attributes" msg

(on a side note - i can't create a 'gemwin' object - i ended up using the 'modular' abstraction version)

@jptrkz
Copy link
Contributor Author

jptrkz commented May 30, 2016

Hi,
glGetActiveAttrib at line 594 in gemvertexbuffer.cpp is returning incorrect GLenums for the attributes. I have two machines running the same version(latest) of gemvertexbuffer, Gem, Pd-Vanilla, and the help file. On the 32 bit machine with OSX10.6 the values are correct and the shaders work, but on the 64 bit machine with OSX10.11 they are wrong and there is no visual output. Even if I edit the function to force the vector sizes to be consistent with the .frag/.vert files in this example, I still get no output. The values before line 594 are all consistent so I have no idea how to investigate further.

@umlaeute
Copy link
Owner

since this PR has been merged, would you mind opening a new issue for any new bugs popping up (including the last one)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants