Spline Demo Crashes

[davebar]

PB 5.72(x64) Win 10 Pro X64
The "spline.pb" demo crashes with the message "program terminated unexpectedly".
Is this a known issue?

[mk-soft]

I don't known ..

But with subsystem OpenGL works

[leonhardt]

update your display driver and try again.

[davebar]

update your display driver and try again.

That is going to be problematic. The issue is identical on 5 different computers.
1. A 5 year old Dell XPS17 laptop with the latest display drivers.
2. A 1 week old Dell XPS17 laptop with the latest display drivers.
3. Three desktop motherboards with nVidia cards and the latest display drivers.

Should I tell nVidia and Dell that Fantaisie Software require that they fix their useless broken drivers?

[Tawbie]

Hi davebar,

I have never used the PB Spline library in my projects but to give you some feedback, I tried running "Spline.pb" from the help file. I got a similar error message "the debugged executable quit unexpectedly" using PB5.72, Windows 10 Pro, on a Surface Pro 4. I doubt whether the drivers are the problem since my Windows 10 Pro updates automatically (and quite frequently too).

[davebar]

Hi davebar,

I have never used the PB Spline library in my projects but to give you some feedback, I tried running "Spline.pb" from the help file. I got a similar error message "the debugged executable quit unexpectedly" using PB5.72, Windows 10 Pro, on a Surface Pro 4. I doubt whether the drivers are the problem since my Windows 10 Pro updates automatically (and quite frequently too).

Hi Tawbie,

Thanks for your feedback. I was about to start using PB for some serious work and the Spline library seemed to be a useful option for part of what I wanted to do. Since the library developers have been unable to produce a working example and I don't have time to reverse engineer the issue, I will now put PB aside for real coding.

[Mijikai]

I only could test PB Version 5.62 x86 & x64 (Windows 10)
The spline example crashes.

[firace]

Just comment out line 19:

Code: Select all

WorldShadows(#PB_Shadow_Modulative, 0, RGB(175, 175, 175))

(IIRC, this is a known issue)

[BarryG]

I will now put PB aside for real coding

Did you specify the OpenGL subsystem in the Compiler Options for the code, like mk-soft said? That should fix the issue.

[davebar]

I will now put PB aside for real coding

Did you specify the OpenGL subsystem in the Compiler Options for the code, like mk-soft said? That should fix the issue.

Thanks for taking the time to respond. The Compiler Options dialog has 5 tabs and none of them offer an "OpenGL Subsystem" option. Care to share the info?

[mk-soft]

I will now put PB aside for real coding

Did you specify the OpenGL subsystem in the Compiler Options for the code, like mk-soft said? That should fix the issue.

Thanks for taking the time to respond. The Compiler Options dialog has 5 tabs and none of them offer an "OpenGL Subsystem" option. Care to share the info?

Is not a CheckBox

Compiler Options -> Library Subsystem: [ ... ] <- OpenGL

[blueb]

Thanks mk-soft,

Adding 'OpenGL' to the Library Subsystem box worked.

Commenting out the offending line as firace suggested does work, I prefer to actually see the shadowing.

[davebar]

OK! So that is the solution, but here is a suggestion for the more experienced, long term PB users (eg. mk-soft, BarryG, etc.). It's great that you guys take the time to answer many questions from mostly new and inexperienced users, but please don't forget that by definition those users do not have your in-depth knowledge and experience of the software. The answer

But with subsystem OpenGL works

was given very early on in this thread by mk-soft, however this doesn't have very much meaning to someone who doesn't have the same knowledge of the software.
Many of the "Examples\3D" files supplied with the PB installer require this OpenGL option to be set. Maybe with the next release a note could be added to the initial comments at the start of those files. I would be happy to add this small instructional comment to those files if required.

[RASHAD]

Hi davebar
Most of the problems with Ogre come's from DirectX
RenderWorld()
WorldShadows()

Just update DirectX maybe your problems will be solved

[davebar]

Hi davebar
Most of the problems with Ogre come's from DirectX
RenderWorld()
WorldShadows()

Just update DirectX maybe your problems will be solved

Hi Rashad,
Updating DirectX would seem like a good idea, but MS don't offer anything other than Version 12, which I already have.
I found several 3D examples with this issue, so I removed the OpenGL compiler option, commented out the "WorldShadows()" line and they all appear to work perfectly.
I haven't found the RenderWorld() to be a problem yet, but thanks for the heads up.