![]() |
|
#1
|
||||
|
||||
|
Has anyone else noticed a problem with qualityStatic in v2.3, at least when the image is scaled? In this case my cube faces are 1500 px for full screen but the comparisons below are from an 800x600 window with a 110 hfov. So, it is scaled down pretty much.
v2.2 didn't do the greatest job in terms of sharpness but at least you didn't get the jaggies. In v2.3 there is essentially no difference between low and best quality here. See the attached comparison. When you zoom the VR in all the way you see a significant difference between low and best quality and best quality looks fine. So the problem is really in this scaled mode.
__________________
Scott Tour de Force 360VR Scott Witte Photography ---------------------- Auto Quality Plugin: Guarantee the best FPP experience possible for every viewer on every computer. Motion Zoom Transition Plugin: Move from Node to Node |
|
#2
|
||||
|
||||
|
Hi Scott
What version of the Adobe Flash Player are you running? As Denis stated when the 2.3 was released: Quote:
|
|
#3
|
||||
|
||||
|
Flash 10. And I did set qualityStatic as Denis described.
Regardless, you can change the quality status using the editor and when zoomed in you see it doing what it should. No AA in low quality with improving results as you increase quality. It is only when zoomed out that the problem appears. So maybe this is more of a scaling problem. But with v2.2 and the same scaling changing quality has a noticeable effect and "best" really does look better. Try it on your own panos (using v2.3 and Flash 10) and see if you get similar results.
__________________
Scott Tour de Force 360VR Scott Witte Photography ---------------------- Auto Quality Plugin: Guarantee the best FPP experience possible for every viewer on every computer. Motion Zoom Transition Plugin: Move from Node to Node |
|
#4
|
||||
|
||||
|
Scott,
I made some tests with a pano of my own (Flash Player 10), and I noticed a funny behaviour. When I set qualityStatic to low in the editor, I can see the pano going into low quality. But as soon as I click the mouse somewhere (in the editor, on the desktop or in another window) the pano leaves low quality mode. And the only way I can get it back into low quality is to first set it to something else then set it back to low. But then, as I said, as soon as I move or touch anything it goes back into high quality. I could see no difference between the medium, high and best settings. And setting qualityStatic2 in the XML file made no difference. Tommy |
|
#5
|
||||
|
||||
|
Quote:
I can't duplicate your problem with quality level not staying put. Are you sure you don't have a command in your file including something like: Code:
<pano onRelease="qualityStatic=high; /> Back to my particular issue, I've attached a more complete example. You can see the problem only occurs when zoomed out. The AA in medium or high or best doesn't perform as well as it did in v2.2. Zoomed in the results are the same between v2.2 and 2.3. As with any anti aliasing, the angle of the line makes a lot of difference in how clearly problems show up. So it may not be obvious with a casual glance. I didn't really notice until I started doing some screen grabs.
__________________
Scott Tour de Force 360VR Scott Witte Photography ---------------------- Auto Quality Plugin: Guarantee the best FPP experience possible for every viewer on every computer. Motion Zoom Transition Plugin: Move from Node to Node |
|
#6
|
||||
|
||||
|
Scott,
you were perfectly right, I did have the onRelease command in my XML. I was totally unaware of that (copy - paste, you know). After having temporarily removed that command, I observed exactly the same effects as you describe. And changing zoom level making quite a difference. Quote:
Tommy |
![]() |
| Thread Tools | |
| Display Modes | |
|
|