Stops working immediately on open Windows 8 64-bit

317 views
Skip to first unread message

Benjamin

unread,
Jan 22, 2015, 7:17:18 PM1/22/15
to ope...@googlegroups.com
- Downloaded
- Extracted
- Attempted to run application and get two "vsp.exe has stopped working" notices as soon as the program opens 

Details:
vsp.exe has stopped working
1st pop up window
Problem signature:
  Problem Event Name: BEX
  Application Name: vsp.exe
  Application Version: 0.0.0.0
  Application Timestamp: 54acc4ba

2nd pop up window
Problem signature:
  Problem Event Name: APPCRASH
  Application Name: vsp.exe
  Application Version: 0.0.0.0
  Application Timestamp: 54acc4ba


Rob McDonald

unread,
Jan 22, 2015, 7:40:22 PM1/22/15
to ope...@googlegroups.com
Hmm,

I don't have a Windows 8 machine to test on. Perhaps others can help
out with this.

Have previous versions worked for you -- or is this your first attempt
with OpenVSP?

I build the Windows version on a Windows 7 64-bit virtual machine --
using Visual Studio Express 2010. The distributed program is a 32-bit
executable.

Is there an option to run it in a compatibility mode?

Rob
> --
> You received this message because you are subscribed to the Google Groups
> "OpenVSP" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to openvsp+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Cale

unread,
May 1, 2015, 1:13:20 PM5/1/15
to ope...@googlegroups.com
Bump this thread....

I'm getting the same problems with Windows 8.1 Pro (32 bit on a 64 bit processor). I've had this issue with all of recent releases and haven't gotten anything to run.

When VSP is launched it gives an error: vsp.exe has stopped working; a problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. I get the same error when trying to run it with Windows 7 compatibility mode. 

It will show the main window and geom browser, but immediately fails and pops the error and closes aftern notification.

Any help would be appreciated!

cale 

Rob McDonald

unread,
May 1, 2015, 3:46:47 PM5/1/15
to ope...@googlegroups.com
Unfortunately, I don't have a Windows 8 machine to test on -- and my
Virtual Machine software doesn't support OpenGL with Windows 8, so
that path got shut down.

I'll keep trying to get ahold of a newer Windows box that I can test with.

Rob

Michael Hubbard

unread,
May 2, 2015, 6:48:29 AM5/2/15
to ope...@googlegroups.com
Rob,

Just wanted mention that I have no problems running your builds on my Windows 8.1 64-bit install.

If I can help narrow down a solution for the others in anyway let me know.

- Mike

Rob McDonald

unread,
May 2, 2015, 10:54:27 AM5/2/15
to ope...@googlegroups.com
Thanks a lot Mike, that is in fact a big help already.

Benjamin & Cale --

The most likely problem is the graphics driver installed on your
machine. Can you run VSP from the command line as a test? This will
make sure the command window stays visible, letting us see any error
messages.

I believe Microsoft's built-in OpenGL support is only good for OpenGL
1.0, and you'll need to install a driver installed by your
manufacturer to support more recent OpenGL features.

Rob

Cale

unread,
May 28, 2015, 11:57:52 PM5/28/15
to ope...@googlegroups.com
Rob,
Thanks for the clues. I have found a fix. It does seem to be related to openGL and a lack of native window support (in windows 8.X) for later versions of openGL. I did a command line run of VSP 3.1.0 and it executed fine. I did a bit of googling for openGL issues related to my particular graphics adapter and was led to this blogpost: https://bigred2162.wordpress.com/2013/07/06/finally-a-fix-for-windows-8-opengl-error/ . A few modifications to suit my particular hardware setup, and I've now got the openVSP GUI running!

Thanks for the pointers. I'm really glad to have gotten this figured out and the latest versions of openVSP up and running on this particular computer. Keep up the good work!

Rob McDonald

unread,
May 29, 2015, 2:00:13 AM5/29/15
to ope...@googlegroups.com
Wow, that looks painful.

Thanks for the perseverance and for reporting back to us a path to make it work.

Rob
Reply all
Reply to author
Forward
0 new messages