Can you please post this query in the Adobe Acrobat forum.
which forum do you mean? though this is the forum for the adobe acrobat reader?!
Thought your issue was with Adobe Acrobat X as mentioned in the first post.
Whilst this is the forum for Adobe Reader.
ok its shift to the "acrobat 3d" discussion. thank for the advice
The floating window and full screen modes do not respect the Default View set on the 3D toolbar. As such you're seeing the internal camera view stored within the 3D file (the one Acrobat would use to make the poster image). A known issue, but don't know if/when it'll be fixed as it's more of a problem for the document author, as the 3D file should have an internal camera which matches the Default View defined in the toolbar menu. If it does, the starting positions will be the same in all three display modes.
hey ok tanks for the answer
but why is it so in version 10? in version 9 (and think in 8 as well) everythink worked fine was is the reason that it was changed in the reader 10 ?
Can you please share a sample file that shows this problem? You may use Acrobat.com or sendbigfile.net to share.
I hope I'd be able to help.
hi good morning,
i was on holiday for 5 days now so sorry my late answer. I tried to set the default view in the u3d model but it doesn't work as well
i loaded up a file that does not work in fullscreen as well as in the floating window (http://www.fileuploadx.de/76685).
In the floating window (or fullscreen) something with the camera must be wrong. I deleted the buttons (you can see as billboards in the scene) and then it works. So i tried to figure out the problem and let me displayed the position of the camera after each rendering event simple by (console.println(scene.cameras.getByIndex(0).position). Even if I displayed all cameras, that were about 50 surprisingly, it was the same overall. If the scene is embedded in the pdf document the camera position changed as it has to be. In the floating window and in the fullscreen i did not record any changes of the camera ...
does anybody has an idea ?!
ps: please use adobe reader 10 to see that issue. with version 9 everythings should work fine.
Issue is reproducible and we are working on it. Thanks for reporting the issue.