With the latest build daily I am getting this message in any file I try to render.
"Python int too large to convert to C long"
LuxCoreRender daily/automatic builds
-
- Posts: 146
- Joined: Sat Feb 22, 2020 3:29 am
Re: LuxCoreRender daily/automatic builds
Are you on Windows ? It doesn't happen for me on Linux. This is likely to be the side effect of a recent change, I pushed a tentative fix but I can not test if it has fixed the problem.JulianoLisboa wrote: ↑Mon Apr 26, 2021 5:10 pm With the latest build daily I am getting this message in any file I try to render.
-
- Posts: 146
- Joined: Sat Feb 22, 2020 3:29 am
Re: LuxCoreRender daily/automatic builds
Yes I use Windows 10, I will test it, thanks.
Re: LuxCoreRender daily/automatic builds
Hi,
Same ""Python int too large to convert to C long"" problem as Juliano on Win10 here on the two latest 2.6 builds (including the latest fix attempt).
Same ""Python int too large to convert to C long"" problem as Juliano on Win10 here on the two latest 2.6 builds (including the latest fix attempt).
Re: LuxCoreRender daily/automatic builds
Actually, I tested the v2.6 build on Windows and it is working fine for me with the default cube, are you using a different test scene ?
Re: LuxCoreRender daily/automatic builds
I have the same python c long error on latest build on laptop. I think it did work on desktop although I'm not sure right now it was the same luxcore build. (both laptop and desktop use ryzen cpu and rtx20xx gpu).
Maybe improper uninstall of blendluxcore could be the cause? For some reason remove option in blender gave me some other python error so I just deleted blendluxcore folder and installed again. I don't know if this could be the cause but 2.5 release version works fine anyways.
Re: LuxCoreRender daily/automatic builds
It is possible to toggle the problem on or off with the following :
Here is the luxball scene with only the Room and LuxBall Center sphere.
By default, all objects have an object Id of -1 (= random Id attribution)
Set the Room Id to 1 in Object Property, leaving the LuxBall Center sphere to -1.
When trying to render, it generates the "Python int too large to convert to C long" error.
When the LuxBall Center sphere object ID is changed to 1, it renders.
It seems that the object ID AOV automatic generation is related to the error.
Hope it helps...
Here is the luxball scene with only the Room and LuxBall Center sphere.
By default, all objects have an object Id of -1 (= random Id attribution)
Set the Room Id to 1 in Object Property, leaving the LuxBall Center sphere to -1.
When trying to render, it generates the "Python int too large to convert to C long" error.
When the LuxBall Center sphere object ID is changed to 1, it renders.
It seems that the object ID AOV automatic generation is related to the error.
Hope it helps...
- Attachments
-
- luxball Python error.blend
- (315.85 KiB) Downloaded 221 times
- foreachthing
- Posts: 1
- Joined: Wed Apr 28, 2021 8:03 pm
Re: LuxCoreRender daily/automatic builds
Got the same thing "Python int too large to convert to C long", posted over at github: https://github.com/LuxCoreRender/BlendL ... issues/674
Re: LuxCoreRender daily/automatic builds
Ok, this explain the problem: Python "int" data type can be 32bit or 64bit long according the value stored. The random ID can assume values larger than 2^31 (it is signed) so Python store the value in a 64bit field and this trigger the problem.mip wrote: ↑Wed Apr 28, 2021 8:28 pm It is possible to toggle the problem on or off with the following :
Here is the luxball scene with only the Room and LuxBall Center sphere.
By default, all objects have an object Id of -1 (= random Id attribution)
Set the Room Id to 1 in Object Property, leaving the LuxBall Center sphere to -1.
When trying to render, it generates the "Python int too large to convert to C long" error.
When the LuxBall Center sphere object ID is changed to 1, it renders.
It seems that the object ID AOV automatic generation is related to the error.
Hope it helps...
I'm now considering all Python "int" as 64bit values and this should have fixed the problem.
Re: LuxCoreRender daily/automatic builds
Working fine now. Thanks Dade !