Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Krom - MacOS - GL Error 1286

See original GitHub issue

Description Target: Krom When the project is compiled, the window is launched, but errors are displayed in the console:

RenderPath - Desktop:

__________  [Armory] Compiling  __________
Exporting Scene
Scene exported in 0.007063150405883789
Finished in 8.375196933746338
deviceBufferSize = 4096
mSampleRate = 44100
mFormatFlags = 00000009
mBytesPerPacket = 8
mFramesPerPacket = 1
mChannelsPerFrame = 2
mBytesPerFrame = 8
mBitsPerChannel = 32

Uniform PPComp11 not found.
Uniform PPComp12 not found.
GL Error 1286 /Users/lubos/Downloads/armorcore/Kinc/Backends/Graphics4/OpenGL/Sources/Kore/OpenGL.cpp 341

#
# Fatal error in v8::Function::Call
# Function to be called is a null pointer
#

RenderPath - Mobile:

__________  [Armory] Compiling  __________
Exporting Scene
Scene exported in 0.006122112274169922
Finished in 6.952546119689941
deviceBufferSize = 4096
mSampleRate = 44100
mFormatFlags = 00000009
mBytesPerPacket = 8
mFramesPerPacket = 1
mChannelsPerFrame = 2
mBytesPerFrame = 8
mBitsPerChannel = 32

GL Error 1286 /Users/lubos/Downloads/armorcore/Kinc/Backends/Graphics4/OpenGL/Sources/Kore/OpenGL.cpp 494
GL Error 1286 /Users/lubos/Downloads/armorcore/Kinc/Backends/Graphics4/OpenGL/Sources/Kore/OpenGL.cpp 341

#
# Fatal error in v8::Function::Call
# Function to be called is a null pointer
#

To Reproduce

Create a project.
Select RenderPath.
Press Play.

System Blender: 2.83.7 Armory: git (e7fd3ce) Device: MacBook Air (11-inch, Mid 2012) OS: MacOS Catalina (10.15.7 (19H2)) Graphics card: Intel HD Graphics 4000 1536 МБ

Test File error.blend.zip

Issue Analytics

State:
Created 3 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

2reactions

MoritzBruecknercommented, Nov 4, 2020

When updating, this script is not updated, since when installing as addons it is located in the corresponding folder of the Blender Foundation and you need to update it or reinstall the addon, thus updating this script.

There is a nice way around that by using symlinks (like shortcuts). This way, the armory.py in the Blender addon directory will be kept up to date with the armoy.py in your SDK.

2reactions

e1e5en-gdcommented, Nov 4, 2020

When i try to export for Linux {Krom): AttributeError: 'ArmoryAddonPreferences' object has no attribute 'open_build_directory'

After updating the SDK, did you reinstall armory.py? Because this setting is specified there and now Render: Armory should look like this: sdk

When updating, this script is not updated, since when installing as addons it is located in the corresponding folder of the Blender Foundation and you need to update it or reinstall the addon, thus updating this script.