I know this sounds really stupid, but when I opened QC for the first time, it looked like the following screenshot and I was seriously thinking something went wrong, until I got the same screen when I installed it in a friends new MBP. Is the splash page supposed to look like that? Or is it something wrong with QC? It looks so ugly and half done! Also, I use Kineme's GL Tools extensively and they dont work in this version of QC. Looking forward for the bug fix and as per cwright's instructions, K3D Beta worked fine.
Also, there are no Mesh Filter examples and the Link from the Splash screen isn't working.
Don't use GLTools, there's a known bug that causes that blackout effect (we're finishing off an update to make that happy again).
Don't use KinemeCore -- it can work for a while, but eventually it'll start causing QC to crash on startup. We're also finishing off an update to make that happy as well...
Awesome! Also, does the welcome screen really look like that? Like a broken HTML page? Just me being a little bit paranoid....
It doesn't have the blackedout regions -- that's a GLTools bug (why we advise not using it, in several places).
Remove the plugin, fire up QC - it's nice and "pretty" (for varying values of "pretty") without it.
There should be some mesh filter examples.... go into the patch creator and type mesh.
qc3 in sl.
Did you just load the old app?
Ok, I went ahead and tried it... cool. I can just browse through my Leopard partition and load the app from my SL partition, without even moving it. Nice one Dust!
Too bad the old patch type look isn't pulled too.
The category section on the patch list is kind of interesting. Nice to see the old dynamic template opener and patch creator.
Oh well. Hmm. Probably not going to roll with QC 3. It's almost a hard call though!!!
I'm kind of at least semi-digging the multi-sample option in QC 4.... can't use that with QC3 as is.
The shadow capability is as cool as it is frustrating for not working with iterators and FOV. DAE mesh rendering doesn't work with FOV either.
The way that state of a render preserves in the viewer when you cut/delete it... really sucks.
It used to really bother me that there was no method of handling aliasing in the app... even though it's smoothed out some, you can still kind of see aliasing. It does look better though. I'm curious exactly what it's doing on that.
you are talking about this. look at top right corner of pic ???? if this is what your talking about it is because you run a see thru editor like me. i thought i would be smart and make a QB desktop app with just a clear patch on it and run it in the background but that didn't work. pressing space bar and moving the grid clears the problem. im thinking it is kineme core that does this, something to do with how it renders the editor. have you tried putting your editor to 0 opacity then click the grid you mouse goes right through it. thought that was cool even though it serves no purpose for editing. i have to set my editor to 6% opacity in order to be able to touch the grid and pan around it.
Oh sorry, I have been unclear perhaps?
{I complained about the cruddy black line around the spaghetti and the way it looks aliased. Well, it did in QC 3 in Leopard as well, but someone thought to make it gray, which makes it less apparent to they eye. Smart move.
You won't really see that noodle outline except for a flash of a second since Opacity in the editor is broken in QC 4(and was in 3 as well, it's just worse now, with the acid trails and whatnot)... unless you run Kinemecore. Seriously though, I was running Kinemecore in SL because on first glance it "seemed" ok, but there are definitely issues, so just beware.}
What I'm ACTUALLY talking about as far as Aliasing goes is the new option in Preferences (option+preferences) for multisampling in the Viewer itself. This really minimizes what we affectionately call "the jaggies". I outlined that on the "Friday..." thread (thanks for the head's up on that Chris, btw).
To enable anti-aliasing/multisampling on supported GPU's in QC 4, hold down option while you are selecting preferences, to open the "hidden" preferences. Go to "Editor"and check off "multisampling". You may have to restart QC for it to take effect... I noted I had to with hidden patches. This may be the case for any change like this now (I don't think it used to be that way?)
Anyway, after a restart of QC, with multisampling enabled, you will see a decent smoothing/anti-aliasing. It's not perfect, but it makes things look a little more polished. Shadows don't seem to respond to the multisampling.
To that, a million thanks to the QC-dev team!
It's not giving me a noticeable hit in performance.
I think that the fellow means hyperlinked examples drawn from the Template screen, GT.
Ok, gotcha. I was surprised about dead link too.
At least they got the patch list link glitches worked out.... I think.
Edit, tee-hee just found that the lion that doesn't roar distro has a revamped selection of developer tools examples which seem greatly diminished from the number available within Leopard 10.5.
Polly-Wollys , there, GT :-)
Did they actually get rid of old ones? I hadn't really noticed yet...
They're all in the Library now (in the Developer folder), not the old Examples location...lumped together more, with different titling... which was the first thing that really weirded me out.
I don't like how there is this overwhelming amount of virtual crud/qtz's as patches, etc. The old composition tool would regularly show me that flattening out, and not loading qtz's as virtual patches is better for performance (though it can be really convenient sometimes). I haven't done any testing in SL to see if that holds.
With all of those qtz's as patches... I kind of feel like I'm working on someone else's personal install! :)
The lion that doesn't roar? I tend to like "Snow Leopard: The Freezinator". (two "fun" moments last night attached).
My default, QC 4(103.1) installation, exhibiting the allegedly elusive Mesh Filter example, a world wide simultaneous release exclusive •~ :-)
Mmm. Co-habitation.
If you look at the left edge of the mesh on the QC 4, you can see the effect of the multisampling smoothing the edge a bit.... but you can also see where it does nothing in other areas.
Angled shadows won't have anti-aliased/multipass effect on shadow edges that are cast onto surfaces either... you still see the jaggy edge when looking at the shadows that are cast.
yeah im going to test and see the multi sampling. i did some testing with parallel computing open cl kernels and well found out mesh files can run just on the cpu as well as apple software render speeds things up so in addition to multi sampling anti-aliasing i have also checked off software open gl rendering as well as the same for core image im not sure if having high resolution core image checked off is going to offset the software rendering but hey seems to work. these are my settings see attached pic. if anybody noticing something that is wrong pleas tell me.
Hi, I also encountered the blackout bug with my own GL-based patch, and I am looking for a clue. Could you give me a hint as to where I should fix?
Are you using GLTools? if so, upgrade to 1.3.
If you're writing a custom plugin, don't base it off of GLTools' codebase. Don't mess with QCOpenGLPort_Blending.
If you're still experiencing problems, I don't know what to tell you -- sounds like you're corrupting GL state or something.
Thank you for your help! I was working on a custom plugin. By commenting out all GL_BLEND related GL state manipulations, the composition is at least visible (with messy alpha). I'm new to GL, so I will go back to the textbooks and manuals and learn the state management.
Ok, that's pretty easy to deal with -- essentially, whatever you change you need to restore before you're done.
So use
glGetIntegerto store the current blend value, set it to whatever you need, do your drawing, then restore the original blend values. It's pretty simple/straightforward. Essentially, your goal is to make it so that the GL state is identical at your function start and end points.Thanks! The composition is becoming similar to what I had in Tiger/Leopard.
Updating the alphablendmode plugin fixes this.