|
blastframe, Newbie
Posted: 23 July 2011 09:30 PM Total Posts: 8
Hello,
I have searched about Away3D anti-aliasing and found that the method is a combination of setting the View3D’s antiAlias property and the html’s wmode to direct. I have done both and my renderer is still very aliased.
I attached a screenshot of my Away3D swf running in Chrome, FP11, on OSX 10.6.7 along side my Actionscript file which shows my code.
This is a test link.
My Mac has an ATI Radeon X1600 graphics card, which supports anti-aliasing.
What could be the problem? Thank you!
|
Richard Olsson, Administrator
Posted: 24 July 2011 08:00 AM Total Posts: 1192
[ # 1 ]
Are you sure that you’re running in direct wmode? Can you try setting antiAlias to 4?
|
blastframe, Newbie
Posted: 24 July 2011 10:45 AM Total Posts: 8
[ # 2 ]
Hi Richard,
Thank you for the reply. My HTML template in Flash Builder did not have wmode set to direct by default, so I changed that so all of my swfobjects would have the wmode param set to ‘direct.’ I’ve set the wmode in three places (see image attached) and changed the anti-aliasing to 4 as you suggested. Still not getting the anti-aliasing. I added AwayStats to verify the GPU is rendering the view. Any other ideas? Thanks.
|
Richard Olsson, Administrator
Posted: 24 July 2011 10:46 AM Total Posts: 1192
[ # 3 ]
|
blastframe, Newbie
Posted: 24 July 2011 10:47 AM Total Posts: 8
[ # 4 ]
Hahahaha! Man, you’re quick! I was previewing the reply and it posted prematurely. Need to get that looked at
I edited the previous post to say everything I wanted to say.
No, it didn’t work. :-( I updated the link I mentioned in the first post if you’d like to have a look.
|
Mr Margaret Scratcher, Sr. Member
Posted: 26 July 2011 01:51 AM Total Posts: 344
[ # 5 ]
There is (or was) a bug in the away stats box that would report HW even though software rendering was being done…
Silly question but you are opening up the html in a browser and not the swf in a browser, right?
|
blastframe, Newbie
Posted: 26 July 2011 07:06 AM Total Posts: 8
[ # 6 ]
Hi and thank you for the reply.
Yes, I do understand there is not a FP11 stand-alone and all Molehill examples must be viewed in an HTML wrapper with wmode set to direct. My compiler argument contains -swf-version=13, minimum player version is set to 11.0.0, and the playerglobal.swc has been changed to the one from the FP11 Beta page.
Your post about the HW-rendering bug makes me think I cannot view HW-accelerated content on my machine. I have an old Macbook Pro from 2006 which has an ATI Radeon X1600 graphics card. I haven’t been able to find any driver updates for it anywhere (maybe there are none). The GPU supposedly supports OpenGL 2.0, but I’m not seeing any of the cool Molehill features.
|
Richard Olsson, Administrator
Posted: 26 July 2011 07:52 AM Total Posts: 1192
[ # 7 ]
That could indeed be the case. Make sure you have the latest version of Away3D from GitHub, as the bug should have been fixed in more recent revisions.
|
Mr Margaret Scratcher, Sr. Member
Posted: 26 July 2011 12:05 PM Total Posts: 344
[ # 8 ]
Easiest way to check I guess is to see if anyone esles projects are being anti aliased is have a look at stuff that is definitely working.
http://www.margaretscratcher.co.uk/VirtualTour/index.html
This is a very simple scene but should be anti aliased….
If that works as you’d expect then it must be something you’re doing wrong.
|