Marius:

Thanks for the help!

Given that I am now having problems with the year-old software that has
worked up until today, your suggestion did not make much sense to me.
However, I did download the snap shot, and it, too fails in the same way
on my proprietary code.  Interestingly, it works with

cube(10);
sphere(10);

I figure something external to OpenSCAD has changed, but I can't imagine
what

Jon

On 3/1/2015 12:42 PM, Marius Kintel wrote:

The attached SCAD file crashes here with the 2015-02-25 snapshot

On 3/1/2015 1:34 PM, Marius Kintel wrote:

That is not at all my proprietary work, LOL!  It was just the first
non-proprietary example that failed, and that I know worked at one time.

My previous  machine was also a Windows 8.1 64 bit machine, but it could
not run OpenGL 2.0.  Before MicroSoft forced me to upgrade from WIn 8.0
to Win 8.1, everything was working well.

I will try playing with this on two other Win 8.1 machines that I have
here, tomorrow.

On 3/1/2015 6:17 PM, MichaelAtOz wrote:

Yes, the octopus came from Thingiverse.

My previous computer was a Win 8.0 64-bit system.  All worked well until
MicroSoft forced me to upgrade from Win 8.0 to Win 8.1, at which point
OpenGL stopped working (unsupported  hardware).  So I doubt that this is
simply a 64-bit bug.  And OpenSCAD continued to work on the old
computer: the visualizations were impossible to use (F5 had artifacts,
and F6 took forever) so I invested in the new hardware.

Please note that the old 2014-03 release worked well for 9 months on the
Windows 8.0 64 bit system.  I am beginning to believe that OpenSCAD has
never worked for non-trivial models on this computer. I just did not
notice it for the last month (did not need to generate those models here).

Very frustrating.

Jon

On 3/1/2015 2:12 PM, Marius Kintel wrote:

I think I found it.  If I enable Compatibility Mode for Win 8, then F6
starts to work again.  I had to do this in both the EXE properties and
the shortcut properties.

Hope this helps.

Jon

On 3/1/2015 8:10 PM, Marius Kintel wrote:

On Mar 2, 2015, at 12:00 PM, jon jon@jonbondy.com wrote:

Thanks - at least another data point.
Do you still have to run as administrator?

If you have time, it would be helpful if you could do this:
o What happens if you try to run as non-administrator?
o Did the compatibility mode behavior or the administrator behavior change recently? Is there any way you could test with which version of OpenSCAD  this behavior changed?

Sorry for putting it all on you, but somehow, it appears that these problems only happen on your computer. I’ve love to be able to reproduce this so we could figure out what happens, but right now, we’re pretty much in the dark.

-Marius

I guess the summary is

• do not check Run As Administrator anywhere in the Properties for the
  EXE file: that will cause an unnecessary dialog to be displayed
• do enable Compatibility Mode for Win 8 in the Properties for the EXE
  file: that will fix the F6 crash
• if you use a shortcut, you may need to do the above for the shortcut, too.

What changed on my system?  No idea.  I moved from an old Win 8.1 system
to a new Win 8.1 system; maybe they were not configured similarly,
without my knowing it.

Jon

On 3/2/2015 1:56 PM, Marius Kintel wrote:

On Mar 2, 2015, at 14:16 PM, jon jon@jonbondy.com wrote:

I guess this is related to Microsoft starting to force developer validation. As we don’t have any dedicated Windows experts on the team this is unlikely to happen soon. The standard workaround is to have an admin unlock the program. This only has to be done once.

This is still puzzling. We’re waiting for others to report similar issues.

-Marius