 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | Rules | You are not logged in.
Hi,
To be able to catch the Windows 7, 64bits browse bug, we setup a generic crash analysis scheme. It will work for any windows version and finally will also help us to find any generic crash not only the quoted one.
So how it works ?
WARNING : This method will only work if you have Autopano Pro or Giga above 2.6.2 RC1 ( version before were not ready for external crash analysis ).
Go here to download the latest version : http://www.kolor.com/download-autopano- … tware.html
* Screenshot 1 : Autopano crash by doing some operation ( typically here, we try to find the windows 7, 64bits folder browser bug ).
DO NOT HIT CANCEL., Wait until windows has created the crash dump.
* Screenshot 2 : Appears after perhaps 1 minute only when he crash dump has been created.
Hit 'Display details' ( afficher les details in French )
* Screenshot 3 : details view
Look at the location where the crash dump has been created. Quite always : C:\User\$your_account\AppData\Local\Temp
There, copy the 3 "WER*" listed files to a new folder on desktop for example. Put them into a zip and send it to us. It will help us to find where the crash occured.
Then and only then, you can hit cancel ( Send the information, would send the issue to Microsoft, not us ).
Offline
I think this may be the same problem, but I'm not sure. I am now unable to render the panos, but just yesterday everything was working fine. I let it sit for 45 minutes (as I ate lunch) and it never gave me the ability to do as the images/instructions in this thread suggest.
Last edited by jeradg (2012-02-03 20:33:28)
Offline
Yes, normal, you are using 2.6.1. This generic crash analysis system has been introduced in 2.6.2 RC1 only.
Offline
I am now using 2.6.2 RC2. If I am unable to render any panos, is there a way to revert to 2.6 so I can complete my work?
Edit: It is now working. I need to do some testing to see if the additional problems (quality of panos) I am having are due to the update or something else I did.
Last edited by jeradg (2012-02-07 18:09:22)
Offline
how about problems like this
this is always when stiching more than 10 panorams
latest stable version /on previous there was NO problem at all/
no matter i use o/c or default CPU settings.
Last edited by pavka (2012-03-24 20:37:20)
Offline
what next
http://imageshack.us/photo/my-images/256/apgcrap.png/
why this is dinal relase not beta???
Last edited by pavka (2012-03-25 16:51:11)
Offline
Do you confirm, you are using 2.6.2 final ?
Issue 1223 opened
Offline
as far i can see its final relase - 
if you want some bug report or smth just let me know how to generate it.
This could be problem with ram and swap file /i have disabled swap file/ and this is happend when i 30+ gb ram is used by APG
Last edited by pavka (2012-03-26 13:46:06)
Offline
Okay. You definitively have OpenGL issue : "NVOGLDC invisible" => means you have an NVidia card and the opengl is not really operationnal.
Could you try to reinstall the graphic card drivers ?
BTW : it is not the right thread to post such answer. Post directly in your own.
Offline
Sometimes, it is really needed to check that focal length provided by images and provided by XML are good and matching. In some case, you just don’t have any focal length. We added an easy way to do that directly in papywizard plugin.
Crash analysis system for Microsoft Windows.
Last edited by mackenzie24 (2013-01-16 16:13:44)
Offline
