For me, fxaa shader post processing has taken it's place (in editor) as it also handles texture moire effect. Kills two birds with one stone.
MSAA is available still via loading the qtz in a simple Xcode project. MSAA was never officially supported, and is a "hidden option". On Dec 17, 2013, at 9:37 AM, Dimitri Delcourt <[email protected]> wrote: > Just a heads up on this issue, > I've found out it was possibly related to the "multisampling" hidden > preference being enabled. > Mixed feelings about not being able to enable that anymore, it is a real > downside for me. > > d. > > > > > On 25 oct. 2013, at 09:34, Achim Breidenbach wrote: > >> Hello Dimitri, >> >> you have to read the crashlog in the crashed thread from bottom up: >> >> lines 66 to 61: usual App-Starting and Run loop >> line 59: _HandleMenuSelection2: you did something with the menu, which leads >> to the next lines: >> 58-44: find the menu item, find the guy who is responsible for it and tell >> him to do something >> 43-40: Obviously this is QC editor (method names from this app is hidden >> from us, so we only see where this code is in memory: >> "com.apple.QuartzComposer.editor 0x000000010b4279a5 0x10b418000 + >> 63909"), >> 41 it should open a file: "openDocumentWithContentsOfURL:" >> 37: "NSWindowController loadWindow" QC Editor ask the system to open a >> window. >> 34: which itself tries to load a resource file (Nib) which contains all the >> information about how the window should look like (com.apple.AppKit loadNib) >> 10: this decoding comes to a point where it has to instantiate a custom >> QC-Editor-Object which gets initialized in line 7. >> 6: [QCView initWithCoder:] shows that this object actually is inherited from >> the QCView, the system class to render and display a composition >> 4: this render view should be initialized [QCView _initializeRenderView] >> 3: but fails:__stack_chk_fail >> >> My guess is, that QC-Editor wants to open up some really big "Viewer" window >> (due to a incorrect parameter found in the "last window size and position" >> storage) and fails to allocate the memory for it, or something like that. >> >> I would go with either the suggestion by Jim, to remove the >> QC-Editor-Preference plist file to get rid of that "last window size and >> position" or for a first step to select the preferences "General > When >> opening a composition > Show only editor" in order to prevent the creation >> of the crashing QCView. >> >> best, >> >> Achim Breidenbach >> Boinx Software Ltd. >> >> >> On 24.10.2013, at 17:15, Dimitri Delcourt <[email protected]> wrote: >> >>> Hi all, >>> >>> I can't open any composition on my 10.8.5 system, not even create a new one. >>> >>> I'm on QC 4.6. I noticed QC 4.6 was installed inside the /Developper >>> directory, and i had to manually remove the graphic tools that were in the >>> /Applications/Dev Tools directory. (Did I create this former directory >>> myself? I can't remember, but i used QC 4.5 successfully for months.) >>> >>> I'm used to node programming, but unfortunately can't decrypt this log. >>> Any help appreciated! >>> >>> dimitri > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Quartzcomposer-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/quartzcomposer-dev/gtoledo3%40gmail.com > > This email sent to [email protected]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [email protected]
