Setup not running correctly.

[tobspr]

Setup not running correctly.

[tobspr]

To use a different version of visual studio, you have to go to rpcore/native/config.ini and set the appropriate visual studio version, e.g. vc_version=Visual Studio 13 2013 I think (If you use cmake --help you can see a list of detected compilers). This should fix the first issue - if it doesn't, please let me know so I can fix it.

For the second issue, I just committed a fix, let me know if it works (I wasn't able to test it yet).

EDIT: Commited another fix

[moonshineTheleocat]

Fantastic! So that fixed the problem of compiling. It both the shaders, and the C++ natives (Visual Studio 12 2013 by the way.)

However, I seem to have run into another problem. It looks like that attempting to run the samples are not successful. I've ran only a few, but the patterns are common enough to show me that it seems to happen at the same point.

http://pastebin.com/ahdcR6ME

There is the log of the command prompt of multiple programs running. I've seperated each attempt by entering multiple spaces before running the next command.

ppython is the python that Panda uses.

http://i.imgur.com/GgBlpQu.png

This is the image of what each program looks like when it crashes.

[tobspr]

Hm its hard to tell, I would need some more information - Can you hit the "Debug" button after the program crashed (the one in your second screenshot) and attach a screenshot what it shows then (You will have to select Visual Studio as a debugger).

(I should probably also remove the warnings about slow loading of assets - It seems your disk seems to be a bit slower, causing each resource to load slowly and thus spam those warnings)

The issue might also be caused by a difference in your Panda3D and the render pipeline build - if its not too much effort, could you try and see if you get the crash with the python modules too?

[moonshineTheleocat]

Welp, now I feel self concious about my hard disk. Then again, the WD Black I had before it went to crap, and the one I got back after claiming it's warranty looked a bit dinged up.

Oh well. I was planning on a new hard drive anyways. Any recommendations?

Anyways. I'll go ahead and try it when I get back. It -could- be a possibility that it's the compilation difference between the two. Given that Panda was compiled using Visual Studios 2015, but the compiler was from the Windows 7.1 SDK. CMAKE apparently doesn't see it, yet it says I have the Visual Studios 10 builder on the platform.

Push comes to shove, I might need to do some changes to VS to change the default compiler.

[moonshineTheleocat]

It looks like it does have to do something with the way the C++ modules are compiled.

Pressing debug however does not provide the most helpful information.

http://i.imgur.com/WhdPpPl.png

That's from a generated file.

[moonshineTheleocat]

I managed to find a copy of visual studios 2010 online, I'm going to try that when I download it. I seriously wander why people have not upgraded to a more recent visual studios =-=, it seems that it's either 2010 or 2012 which are incredibly hard to find now, or no longer supported.

[rdb]

For what it's worth, the reason why Panda3D is still compiled with MSVC 2010 is because it's the last compiler to still support Windows XP, which still makes up a non-negligible portion of Panda3D's user base.

If that wasn't the issue, we'd already be on MSVC 2015.

[moonshineTheleocat]

Alright I got it working.

Definitely the easiest way was to download Visual Studios 2010 then to fool with everything else.

It seems things are really washed out and flickering. I doubt the problem is in my hardware as it plays most current games, and runs editors just fine without problems. Could it be a problem with the Glsl? shaders?

http://i.imgur.com/r2zlzlK.jpg

http://pastebin.com/x7JA8ZsZ

[tobspr]

Hm, well yeah I guess the issue was that something was different in your Panda3D build than the render pipeline native build.

About the the flickering - I will have a look at it when I come home, maybe the GLSL warnings you get are related.

[tobspr]

@moonshineTheleocat which drivers are you using btw? It seems your driver is a bit weird, do you have a chance to try a newer version? Also which GPU do you use?

[moonshineTheleocat]

AMD HD7950

Driver Packaging Version
16.15.2211

OpenGL® Version
6.14.10.13431

Also, is it possible that I can use an "issue" to open up a discussion? Or do you have one else where? I'd like to ask a few questions about the implementation.

I'd like to make some suggestions that may help out with the performance and drop memory usage. Though mind you, I'm not a professional graphics programmer. Just a student looking to make his own rendering system.

[tobspr]

I just committed a fix for your GLSL warnings - let me know if it works for you, maybe the other issues you were getting are related.

I'm just a student too - if you have any suggestions/improvements then feel free to open another issue :) Same goes for questions - they are not really issues, but that should be fine, this way others can also see the answers.