J
jon
Fri, Mar 13, 2015 4:25 PM
My proprietary model is crashing again. Sometimes it works, sometimes
not, depending on the parameters that I apply to it (which, of course,
changes the geometry).
Sure would be nice if it didn't just crash, but rather gave even a HINT
at what was going wrong and/or what I could consider changing. Very
frustrating having F5 work and F6 take 30 minutes to crash. I'm wasting
a LOT of time trying different things blindly.
Argh
Jon
My proprietary model is crashing again. Sometimes it works, sometimes
not, depending on the parameters that I apply to it (which, of course,
changes the geometry).
Sure would be nice if it didn't just crash, but rather gave even a HINT
at what was going wrong and/or what I could consider changing. Very
frustrating having F5 work and F6 take 30 minutes to crash. I'm wasting
a LOT of time trying different things blindly.
Argh
Jon
MK
Marius Kintel
Fri, Mar 13, 2015 6:40 PM
My proprietary model is crashing again. Sometimes it works, sometimes not, depending on the parameters that I apply to it (which, of course, changes the geometry).
Could you provide a crashing example again?
-Marius
On Mar 13, 2015, at 12:25 PM, jon <jon@jonbondy.com> wrote:
> My proprietary model is crashing again. Sometimes it works, sometimes not, depending on the parameters that I apply to it (which, of course, changes the geometry).
>
Could you provide a crashing example again?
-Marius
J
jon
Fri, Mar 13, 2015 6:53 PM
Not a simple one. Seems that if I increase any of the $ values, it
crashes. I had to reduce the fidelity of the model significantly to get
it to create.
I am fine with limitations on the fidelity. It is the time consuming
nature of this, and the fact that I'm working in the dark, that is
frustrating.
Jon
On 3/13/2015 2:40 PM, Marius Kintel wrote:
My proprietary model is crashing again. Sometimes it works, sometimes not, depending on the parameters that I apply to it (which, of course, changes the geometry).
Not a simple one. Seems that if I increase any of the $ values, it
crashes. I had to reduce the fidelity of the model significantly to get
it to create.
I am fine with limitations on the fidelity. It is the time consuming
nature of this, and the fact that I'm working in the dark, that is
frustrating.
Jon
On 3/13/2015 2:40 PM, Marius Kintel wrote:
> On Mar 13, 2015, at 12:25 PM, jon <jon@jonbondy.com> wrote:
>
>> My proprietary model is crashing again. Sometimes it works, sometimes not, depending on the parameters that I apply to it (which, of course, changes the geometry).
>>
> Could you provide a crashing example again?
>
> -Marius
>
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2015.0.5751 / Virus Database: 4306/9292 - Release Date: 03/13/15
>
>
DL
David Lucero
Fri, Mar 13, 2015 6:55 PM
Try changing the view to Grid Only (F11) before rendering (F6)? Sometimes,
for me, it's the preview window that can't handle it.
On Fri, Mar 13, 2015 at 1:53 PM, jon jon@jonbondy.com wrote:
Not a simple one. Seems that if I increase any of the $ values, it
crashes. I had to reduce the fidelity of the model significantly to get it
to create.
I am fine with limitations on the fidelity. It is the time consuming
nature of this, and the fact that I'm working in the dark, that is
frustrating.
Jon
On 3/13/2015 2:40 PM, Marius Kintel wrote:
On Mar 13, 2015, at 12:25 PM, jon jon@jonbondy.com wrote:
My proprietary model is crashing again. Sometimes it works, sometimes
not, depending on the parameters that I apply to it (which, of course,
changes the geometry).
Could you provide a crashing example again?
Try changing the view to Grid Only (F11) before rendering (F6)? Sometimes,
for me, it's the preview window that can't handle it.
On Fri, Mar 13, 2015 at 1:53 PM, jon <jon@jonbondy.com> wrote:
> Not a simple one. Seems that if I increase any of the $ values, it
> crashes. I had to reduce the fidelity of the model significantly to get it
> to create.
>
> I am fine with limitations on the fidelity. It is the time consuming
> nature of this, and the fact that I'm working in the dark, that is
> frustrating.
>
> Jon
>
>
> On 3/13/2015 2:40 PM, Marius Kintel wrote:
>
>> On Mar 13, 2015, at 12:25 PM, jon <jon@jonbondy.com> wrote:
>>
>> My proprietary model is crashing again. Sometimes it works, sometimes
>>> not, depending on the parameters that I apply to it (which, of course,
>>> changes the geometry).
>>>
>>> Could you provide a crashing example again?
>>
>> -Marius
>>
>>
>> _______________________________________________
>> OpenSCAD mailing list
>> Discuss@lists.openscad.org
>> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>>
>>
>>
>> -----
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2015.0.5751 / Virus Database: 4306/9292 - Release Date: 03/13/15
>>
>>
>>
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>
AP
Andrew Plumb
Fri, Mar 13, 2015 6:59 PM
For more complex, high-polygon count designs, sometimes it helps to explicitly insert render() operations to flatten a level or three of hierarchy.
Andrew
Sent from my iPhone
On Mar 13, 2015, at 14:53, jon jon@jonbondy.com wrote:
Not a simple one. Seems that if I increase any of the $ values, it crashes. I had to reduce the fidelity of the model significantly to get it to create.
I am fine with limitations on the fidelity. It is the time consuming nature of this, and the fact that I'm working in the dark, that is frustrating.
Jon
On 3/13/2015 2:40 PM, Marius Kintel wrote:
On Mar 13, 2015, at 12:25 PM, jon jon@jonbondy.com wrote:
My proprietary model is crashing again. Sometimes it works, sometimes not, depending on the parameters that I apply to it (which, of course, changes the geometry).
For more complex, high-polygon count designs, sometimes it helps to explicitly insert render() operations to flatten a level or three of hierarchy.
Andrew
Sent from my iPhone
> On Mar 13, 2015, at 14:53, jon <jon@jonbondy.com> wrote:
>
> Not a simple one. Seems that if I increase any of the $ values, it crashes. I had to reduce the fidelity of the model significantly to get it to create.
>
> I am fine with limitations on the fidelity. It is the time consuming nature of this, and the fact that I'm working in the dark, that is frustrating.
>
> Jon
>
>> On 3/13/2015 2:40 PM, Marius Kintel wrote:
>>> On Mar 13, 2015, at 12:25 PM, jon <jon@jonbondy.com> wrote:
>>>
>>> My proprietary model is crashing again. Sometimes it works, sometimes not, depending on the parameters that I apply to it (which, of course, changes the geometry).
>> Could you provide a crashing example again?
>>
>> -Marius
>>
>>
>> _______________________________________________
>> OpenSCAD mailing list
>> Discuss@lists.openscad.org
>> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>>
>>
>>
>> -----
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2015.0.5751 / Virus Database: 4306/9292 - Release Date: 03/13/15
>
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
MK
Marius Kintel
Fri, Mar 13, 2015 7:02 PM
Not a simple one. Seems that if I increase any of the $ values, it crashes. I had to reduce the fidelity of the model significantly to get it to create.
It’s likely not related to increased resolution at all. We should never crash and crash bugs have high priority, so I’m willing to dig quite a bit to help you out.
-Marius
On Mar 13, 2015, at 14:53 PM, jon <jon@jonbondy.com> wrote:
> Not a simple one. Seems that if I increase any of the $ values, it crashes. I had to reduce the fidelity of the model significantly to get it to create.
>
It’s likely not related to increased resolution at all. We should never crash and crash bugs have high priority, so I’m willing to dig quite a bit to help you out.
-Marius
J
jon
Fri, Mar 13, 2015 11:49 PM
I will do a careful study next week, writing down the parameters and
noting the results. At the moment, my impression is that these crashes
occur erratically, unpredictably. At 30 minutes per run, it will take
some time.
Jon
On 3/13/2015 3:02 PM, Marius Kintel wrote:
Not a simple one. Seems that if I increase any of the $ values, it crashes. I had to reduce the fidelity of the model significantly to get it to create.
I will do a careful study next week, writing down the parameters and
noting the results. At the moment, my impression is that these crashes
occur erratically, unpredictably. At 30 minutes per run, it will take
some time.
Jon
On 3/13/2015 3:02 PM, Marius Kintel wrote:
> On Mar 13, 2015, at 14:53 PM, jon <jon@jonbondy.com> wrote:
>
>> Not a simple one. Seems that if I increase any of the $ values, it crashes. I had to reduce the fidelity of the model significantly to get it to create.
>>
> It’s likely not related to increased resolution at all. We should never crash and crash bugs have high priority, so I’m willing to dig quite a bit to help you out.
>
> -Marius
>
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2015.0.5751 / Virus Database: 4306/9292 - Release Date: 03/13/15
>
>
>
MK
Marius Kintel
Sat, Mar 14, 2015 4:04 PM
I will do a careful study next week, writing down the parameters and noting the results. At the moment, my impression is that these crashes occur erratically, unpredictably. At 30 minutes per run, it will take some time.
Is this still on 64-bit Win 8.1 using Win 8 compatibility mode?
-Marius
On Mar 13, 2015, at 19:49 PM, jon <jon@jonbondy.com> wrote:
> I will do a careful study next week, writing down the parameters and noting the results. At the moment, my impression is that these crashes occur erratically, unpredictably. At 30 minutes per run, it will take some time.
>
Is this still on 64-bit Win 8.1 using Win 8 compatibility mode?
-Marius
J
jon
Sat, Mar 14, 2015 4:14 PM
Yes, WIn 8.1 64-bit. Not sure whether using compatibility mode (Win 8
or Win 7) is useful or not yet.
Jon
On 3/14/2015 12:04 PM, Marius Kintel wrote:
I will do a careful study next week, writing down the parameters and noting the results. At the moment, my impression is that these crashes occur erratically, unpredictably. At 30 minutes per run, it will take some time.
Yes, WIn 8.1 64-bit. Not sure whether using compatibility mode (Win 8
or Win 7) is useful or not yet.
Jon
On 3/14/2015 12:04 PM, Marius Kintel wrote:
> On Mar 13, 2015, at 19:49 PM, jon <jon@jonbondy.com> wrote:
>
>> I will do a careful study next week, writing down the parameters and noting the results. At the moment, my impression is that these crashes occur erratically, unpredictably. At 30 minutes per run, it will take some time.
>>
> Is this still on 64-bit Win 8.1 using Win 8 compatibility mode?
>
> -Marius
>
>
> _______________________________________________
> OpenSCAD mailing list
> Discuss@lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2015.0.5751 / Virus Database: 4306/9299 - Release Date: 03/14/15
>
>
MK
Marius Kintel
Sat, Mar 14, 2015 4:27 PM
Yes, WIn 8.1 64-bit. Not sure whether using compatibility mode (Win 8 or Win 7) is useful or not yet.
Ok.
The first step for us would be to validate that the crash is not unique to your computer, since last time, nobody was able to reproduce the problem.
Even though I don’t have access to 64-bit Windows, there are tons of helpful people on this list who are ready to test stuff given the chance.
-Marius
On Mar 14, 2015, at 12:14 PM, jon <jon@jonbondy.com> wrote:
> Yes, WIn 8.1 64-bit. Not sure whether using compatibility mode (Win 8 or Win 7) is useful or not yet.
>
Ok.
The first step for us would be to validate that the crash is not unique to your computer, since last time, nobody was able to reproduce the problem.
Even though I don’t have access to 64-bit Windows, there are tons of helpful people on this list who are ready to test stuff given the chance.
-Marius
