Open GL Errors

[Aaron Maurer]

Hi all.  I was running older versions of OpenVSP (2.X.X), I have since downloaded and tried to run 3.X.X which crashes upon opening.  The command prompt window shows that my driver is out of data and my open GL version is 1.4.  My graphics drivers are the latest available for my machine (cira 2010 Windows 7 Laptop).  What do I do?

[Rob McDonald]

Oh no. Nobody should be running 2.X anymore!

Your machine and Windows 7 should be entirely fine. OpenGL 1.4 is in
fact quite old (2002).

The fix to this problem is to update or fix your graphics drivers.
Are you sure you're running the latest driver? Does your card give a
choice of whether the driver is best for DirectX or OpenGL?

Did you get the updated driver from Microsoft, or from your video card
company (NVidia, ATI, AMD, etc?).

Even the Microsoft default drivers for Win 7 should support 1.4 -- it
wasn't until Windows 8 or 10 that they crippled the default drivers to
strictly 1.0.

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.

[Trevor Laughlin]

I doubt this is the issue, but just in case it leads you to a solution I can tell you a problem I had running Windows 10...

I typically use my laptop connected to external monitors via a USB docking station and turn off the monitor on the laptop. Up until early August I never experienced any issues with OpenVSP, then Windows rolled out an "Anniversary Update" and OpenVSP would crash on start-up and the attached errors were present in the command prompt. Long story short, when the laptop monitor is turned off some applications can't find the graphics driver on the laptop and I guess use the driver on the docking station itself, which apparently doesn't support the version of OpenGL that VSP needs. Simply turning the laptop monitor back on (in extended mode) resolves the issue.

Trevor

[Rob McDonald]

That is very interesting.

Some laptops have two graphics chips -- my Mac has an integrated Intel
chip and also a stand-alone NVidia chip. The Intel chip isn't as
fast, but it uses less power. My Mac switches back and forth
depending on how demanding it judges the graphics needs of the
application are -- and on your current power saving state.

On a Windows machine like this, I would expect that you would actually
need to have two graphics drivers -- one for each chip. In that case,
you should be able to update both of them to the latest from the chip
vendor (not Microsoft) and OpenVSP should work either way.

Rob

[Martin Simon]

Hello Rob,

I am experiencing somewhat similar problems on Ubuntu 16.04.
Opening a .vsp3 file used to be instant with the 3.4 version.
Using 3.11 it first crashed with an error:
"Current driver does not support Vertex Buffer Object.OpenGL version reports: 4.5.0 NVIDIA 375.26"

After I added #include <stdio.h>  at the top of VBO.cpp and reinstalled it again the error mostly stopped, but now it takes ca 1 minute to open a file.

Any ideas? :)

Thanks!
Martin

[Rob McDonald]

Martin,

These things don't make any sense and must be unrelated.

Adding #include <stdio.h> to a file that successfully compiled without
it shouldn't make a difference. It certainly wouldn't change which
OpenGL drivers got loaded by the operating system.

If the model is slow to load, it may just be the model -- is it also
slow to update?

Many laptops with two GPU's will switch which one is active depending
on power state (plugged in or battery) and also external monitor state
-- did these things change through your test?

Rob

[Martin Simon]

Makes sense.

I just tested running the standard script Wing.vspscript on both 3.11 and 3.4.1.

On 3.11 it took ca 1 minute, while on 3.4.1 it is almost instantaneous.

Both were done with the same GPU and with NVIDIA Driver Version: 375.26.

best regards,

Martin

> email to openvsp+unsubscribe@googlegroups.com.

> For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to a topic in the Google Groups "OpenVSP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openvsp/tnoQz88P8YU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openvsp+unsubscribe@googlegroups.com.

[Rob McDonald]

Ok, I bet I know what most of the slowdown is -- you aren't going to like it.

You need to compile everything again!

By default, CMake builds everything in Debug mode -- which is much
slower. You need to go back and re-run CMake with
-DCMAKE_BUILD_TYPE=Release as an additional option.

Rob

>> You received this message because you are subscribed to a topic in the
>> Google Groups "OpenVSP" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/openvsp/tnoQz88P8YU/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to

[Martin Simon]

Awesome! Works now. I will document the final build set up for Ubuntu 16.04 on the Wiki.

Thanks!

Martin

>> > email to openvsp+unsubscribe@googlegroups.com.

>> > For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "OpenVSP" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/openvsp/tnoQz88P8YU/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to

>> openvsp+unsubscribe@googlegroups.com.

>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> 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+unsubscribe@googlegroups.com.

> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "OpenVSP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openvsp/tnoQz88P8YU/unsubscribe.

To unsubscribe from this group and all its topics, send an email to openvsp+unsubscribe@googlegroups.com.

[Rob McDonald]

Martin,

I've had some more questions about Ubuntu 16.04 -- even if you don't
have time to update the Wiki, a few notes here on how you overcame the
problems you had will be much appreciated.

Rob

>> >> You received this message because you are subscribed to a topic in the
>> >> Google Groups "OpenVSP" group.
>> >> To unsubscribe from this topic, visit
>> >> https://groups.google.com/d/topic/openvsp/tnoQz88P8YU/unsubscribe.
>> >> To unsubscribe from this group and all its topics, send an email to

>> >> openvsp+u...@googlegroups.com.
>> >> For more options, visit https://groups.google.com/d/optout.
>> >
>> >
>> > --
>> > 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.
>>
>> --

>> You received this message because you are subscribed to a topic in the
>> Google Groups "OpenVSP" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/openvsp/tnoQz88P8YU/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to

[Martin Simon]

Hello Rob!

Sorry for the delay. I just updated the Ubuntu installation Wiki. The 16.04 part is what worked for me.

Although I get the error of

VSPAERO solver not found. VSPAERO viewer not found

when using Python API, everything else works as a charm.

Best regards,

Martin Simon

>> >> > email to openvsp+unsubscribe@googlegroups.com.

>> >> > For more options, visit https://groups.google.com/d/optout.
>> >>
>> >> --
>> >> You received this message because you are subscribed to a topic in the
>> >> Google Groups "OpenVSP" group.
>> >> To unsubscribe from this topic, visit
>> >> https://groups.google.com/d/topic/openvsp/tnoQz88P8YU/unsubscribe.
>> >> To unsubscribe from this group and all its topics, send an email to

>> >> openvsp+unsubscribe@googlegroups.com.

>> >> For more options, visit https://groups.google.com/d/optout.
>> >
>> >
>> > --
>> > 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+unsubscribe@googlegroups.com.

>> > For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "OpenVSP" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/openvsp/tnoQz88P8YU/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to

>> openvsp+unsubscribe@googlegroups.com.

>> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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+unsubscribe@googlegroups.com.

> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "OpenVSP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openvsp/tnoQz88P8YU/unsubscribe.

To unsubscribe from this group and all its topics, send an email to openvsp+unsubscribe@googlegroups.com.

[Rob McDonald]

When VSP starts (even the Python API module), it searches for the VSPAERO solver and viewer executable -- in the same place as the VSP binary (so probably wherever the python vsp.so is located).

If it can't find them, it prints out those messages -- harmless unless you want to run VSPAERO through the API.

Thanks for the work updating the instructions, I'll check them out.

Rob

[Martin Simon]

Hello Rob,

the VSPAERO and viewer solvers in the same path as the vsp.so like on the attached picture.
I am using the API as a part of optimization, where I send information about the setup and receive the results, but at the moment I am doing it by writing and reading VSPAERO related documents. :)

Best regards,

Martin