[SOLVED] Jme-Vehicles Failed to run

Pavl_G · February 15, 2021, 11:22am

Hi @sgold , i have cloned jme-Vehicles the latest , build is fine , but when trying to run , it opens fine , jaime animation displays , then i ses the car for less than 1 second & the game crashes with logs :

java.lang.UnsupportedOperationException: No technique 'Default' on material 'Afflicted PBR Terrain' is supported by the video hardware. The capabilities [GLSL150] are required.
	at com.jme3.material.Material.selectTechnique(Material.java:770)
	at com.jme3.renderer.RenderManager.renderGeometry(RenderManager.java:599)
	at com.jme3.renderer.queue.RenderQueue.renderGeometryList(RenderQueue.java:266)
	at com.jme3.renderer.queue.RenderQueue.renderShadowQueue(RenderQueue.java:275)
	at com.jme3.shadow.AbstractShadowRenderer.renderShadowMap(AbstractShadowRenderer.java:439)
	at com.jme3.shadow.AbstractShadowRenderer.postQueue(AbstractShadowRenderer.java:412)
	at com.jme3.renderer.RenderManager.renderViewPort(RenderManager.java:1103)
	at com.jme3.renderer.RenderManager.render(RenderManager.java:1158)
	at com.jme3.app.SimpleApplication.update(SimpleApplication.java:272)
	at com.jme3.system.lwjgl.LwjglWindow.runLoop(LwjglWindow.java:530)
	at com.jme3.system.lwjgl.LwjglWindow.run(LwjglWindow.java:632)
	at com.jme3.system.lwjgl.LwjglWindow.create(LwjglWindow.java:466)
	at com.jme3.app.LegacyApplication.start(LegacyApplication.java:463)
	at com.jme3.app.LegacyApplication.start(LegacyApplication.java:424)
	at com.jme3.app.SimpleApplication.start(SimpleApplication.java:127)
	at com.jayfella.jme.vehicle.lemurdemo.MavDemo1.main(MavDemo1.java:227)

as i understand my laptop graphic card driver openGL3.0 mesa doesnot support the technique used by a physics world , the problem is i cannot find the shader Afflicted PBR Terrain , i must replace it w/ the standard PBRLighting.j3md instead or must i do something else . Any Clue ?? i hope , i can edit it through code , not the SDK(as i would have to render it , which i really cannot)

thanks,

my drivers are :

INFO: OpenGL Renderer Information
 * Vendor: Intel Open Source Technology Center
 * Renderer: Mesa DRI Intel(R) Kabylake GT2F 
 * OpenGL Version: 3.0 Mesa 19.3.3
 * GLSL Version: 1.30
 * Profile: Compatibility

NB ; i run both Mavdemo1 & HelloMav runnable classes , both of which , gives me the same exception

EDIT :
Tried to open vehicle-playground.j3o through the JME-SDK i got this exception :

Ali_RS · February 15, 2021, 3:20pm

Can you try with OpenGL 3 core profile.

You need to set this on AppSettings:
settings.setRenderer(AppSettings.LWJGL_OPENGL32);

Also does your laptop have a dedicated graphics card (AMD or NVidia)?

Pavl_G · February 15, 2021, 4:12pm

No.

I will try.

Pavl_G · February 15, 2021, 7:55pm

com.jme3.renderer.RendererException: Shader failed to link, shader:Shader[numSources=2, numUniforms=85, numBufferBlocks=0, shaderSources=[ShaderSource[name=MatDefs/frag/AfflictedPBRTerrain.frag, defines, type=Fragment, language=GLSL150], ShaderSource[name=MatDefs/vert/AfflictedPBRTerrain.vert, defines, type=Vertex, language=GLSL150]]]
error: fragment shader input `wTangent' has no matching output in the previous stage

	at com.jme3.renderer.opengl.GLRenderer.updateShaderData(GLRenderer.java:1564)
	at com.jme3.renderer.opengl.GLRenderer.setShader(GLRenderer.java:1576)
	at com.jme3.material.logic.SinglePassAndImageBasedLightingLogic.render(SinglePassAndImageBasedLightingLogic.java:259)
	at com.jme3.material.Technique.render(Technique.java:166)
	at com.jme3.material.Material.render(Material.java:1026)
	at com.jme3.renderer.RenderManager.renderGeometry(RenderManager.java:614)
	at com.jme3.renderer.queue.RenderQueue.renderGeometryList(RenderQueue.java:266)
	at com.jme3.renderer.queue.RenderQueue.renderQueue(RenderQueue.java:305)
	at com.jme3.renderer.RenderManager.renderViewPortQueues(RenderManager.java:877)
	at com.jme3.renderer.RenderManager.flushQueue(RenderManager.java:779)
	at com.jme3.renderer.RenderManager.renderViewPort(RenderManager.java:1108)
	at com.jme3.renderer.RenderManager.render(RenderManager.java:1158)
	at com.jme3.app.SimpleApplication.update(SimpleApplication.java:272)
	at com.jme3.system.lwjgl.LwjglWindow.runLoop(LwjglWindow.java:530)
	at com.jme3.system.lwjgl.LwjglWindow.run(LwjglWindow.java:632)
	at com.jme3.system.lwjgl.LwjglWindow.create(LwjglWindow.java:466)
	at com.jme3.app.LegacyApplication.start(LegacyApplication.java:463)
	at com.jme3.app.LegacyApplication.start(LegacyApplication.java:424)
	at com.jme3.app.SimpleApplication.start(SimpleApplication.java:127)
	at com.jayfella.jme.vehicle.lemurdemo.MavDemo1.main(MavDemo1.java:227)


Process finished with exit code 1

it uses GLSL150 , my device’s Shader preprocessor is GLSL130 , so no way to run this version without removing AflictedPBRTerrain.j3md from the playground , anyway i have my old fork in PBRLighting.j3md & its working fine . thanks

sgold · February 15, 2021, 8:27pm

The vehicle-playground world uses the standard “PBR Lighting” material definitions, not the @yaRnMcDonuts “PBR Terrain” definitions. (The world using PBR Terrain is the one named “Mountains”.)

Since “Mountains” is the initial world for both “HelloMav” and “MavDemo1”, this issue is going to block you from running both apps. Sorry!

yaRnMcDonuts · February 15, 2021, 9:07pm

I will fix this to also allow your version, this must have been a mistake I made while working on the advanced shader that required glsl150 + for texture arrays, but the basic copy of the shader doesnt need them so I should be able to add an allowance for lower versions. I will try to update the code asap. My apologies for breaking the MAV app for you.

yaRnMcDonuts · February 16, 2021, 12:22am

I just uploaded a version that should work for you now, let me know if it gives you any trouble still.

sgold · February 16, 2021, 12:52am

Thanks, @yaRnMcDonuts ! I updated the jme-vehicles build script to use the new version of PBR Terrain.

Pavl_G · February 16, 2021, 9:22am

Thank you both , seems the problem is with my laptop , i have changed the AfflictedPBR to use v1.0.2 but i get this exception :

SEVERE: Uncaught exception thrown in Thread[main,5,main]
com.jme3.renderer.RendererException: Shader failed to link, shader:Shader[numSources=2, numUniforms=85, numBufferBlocks=0, shaderSources=[ShaderSource[name=MatDefs/frag/AfflictedPBRTerrain.frag, defines, type=Fragment, language=GLSL130], ShaderSource[name=MatDefs/vert/AfflictedPBRTerrain.vert, defines, type=Vertex, language=GLSL130]]]
error: fragment shader input `wTangent' has no matching output in the previous stage

	at com.jme3.renderer.opengl.GLRenderer.updateShaderData(GLRenderer.java:1564)
	at com.jme3.renderer.opengl.GLRenderer.setShader(GLRenderer.java:1576)
	at com.jme3.material.logic.SinglePassAndImageBasedLightingLogic.render(SinglePassAndImageBasedLightingLogic.java:259)
	at com.jme3.material.Technique.render(Technique.java:166)
	at com.jme3.material.Material.render(Material.java:1026)
	at com.jme3.renderer.RenderManager.renderGeometry(RenderManager.java:614)
	at com.jme3.renderer.queue.RenderQueue.renderGeometryList(RenderQueue.java:266)
	at com.jme3.renderer.queue.RenderQueue.renderQueue(RenderQueue.java:305)
	at com.jme3.renderer.RenderManager.renderViewPortQueues(RenderManager.java:877)
	at com.jme3.renderer.RenderManager.flushQueue(RenderManager.java:779)
	at com.jme3.renderer.RenderManager.renderViewPort(RenderManager.java:1108)
	at com.jme3.renderer.RenderManager.render(RenderManager.java:1158)
	at com.jme3.app.SimpleApplication.update(SimpleApplication.java:272)
	at com.jme3.system.lwjgl.LwjglWindow.runLoop(LwjglWindow.java:530)
	at com.jme3.system.lwjgl.LwjglWindow.run(LwjglWindow.java:632)
	at com.jme3.system.lwjgl.LwjglWindow.create(LwjglWindow.java:466)
	at com.jme3.app.LegacyApplication.start(LegacyApplication.java:463)
	at com.jme3.app.LegacyApplication.start(LegacyApplication.java:424)
	at com.jme3.app.SimpleApplication.start(SimpleApplication.java:127)
	at com.jayfella.jme.vehicle.lemurdemo.MavDemo1.main(MavDemo1.java:224)

So, i have deactivated Mountains world , & used the Racetrack as default .

yaRnMcDonuts · February 16, 2021, 10:11am

The problem is actually on my end again I think. A friend that was testing my game actually had the same error with the ‘wtangent’ variable recently, but I procrastinated fixing it, since they were not running the app in an IDE and they couldn’t find the error in the logs to give me a complete error message as you have, which meant I had no clue which of my shaders was causing it. So i appreciate your help finding this bug.

Shader versions can be tricky to work with sometimes, since a minor mistake in shader code can slip by depending on the version of GLSL and the GPU the developer is using, but will still cause crashes like this on other GPUs. I will try to fix it and re-upload again soon, since it should be an easy fix.

Pavl_G · February 16, 2021, 10:13am

Just ping me here , to test it

yaRnMcDonuts · February 20, 2021, 4:40am

@Pavl_G I’ve just uploaded a new version 1.0.3 to bintray that should fix the error. I’ve also cleaned up the shaders to remove any other unused variables and defines I left laying around that could also cause more issues on other glsl versions - it should all work now, but let me know if it causes anymore trouble for you.

Pavl_G · February 20, 2021, 5:42pm

com.jme3.asset.AssetLoadException: An exception has occurred while loading asset: /Materials/Vehicles/Mountains.j3m
	at com.jme3.asset.DesktopAssetManager.loadLocatedAsset(DesktopAssetManager.java:262)
	at com.jme3.asset.DesktopAssetManager.loadAsset(DesktopAssetManager.java:374)
	at com.jme3.asset.DesktopAssetManager.loadMaterial(DesktopAssetManager.java:395)
	at com.jayfella.jme.vehicle.examples.worlds.Mountains.load(Mountains.java:98)
	at com.jayfella.jme.vehicle.gui.menu.WorldMenu.setWorld(WorldMenu.java:71)
	at com.jayfella.jme.vehicle.gui.menu.WorldMenu.lambda$createItems$1(WorldMenu.java:46)
	at com.simsilica.lemur.core.CommandMap.runCommands(CommandMap.java:61)
	at com.simsilica.lemur.Button.runClick(Button.java:359)
	at com.simsilica.lemur.Button$ButtonMouseHandler.mouseButtonEvent(Button.java:436)
	at com.simsilica.lemur.event.MouseEventControl.mouseButtonEvent(MouseEventControl.java:122)
	at com.simsilica.lemur.event.PickEventSession.buttonEvent(PickEventSession.java:657)
	at com.simsilica.lemur.event.MouseAppState.dispatch(MouseAppState.java:98)
	at com.simsilica.lemur.event.MouseAppState$MouseObserver.onMouseButtonEvent(MouseAppState.java:114)
	at com.jme3.input.InputManager.processQueue(InputManager.java:841)
	at com.jme3.input.InputManager.update(InputManager.java:917)
	at com.jme3.app.LegacyApplication.update(LegacyApplication.java:724)
	at com.jme3.app.SimpleApplication.update(SimpleApplication.java:246)
	at com.jme3.system.lwjgl.LwjglWindow.runLoop(LwjglWindow.java:530)
	at com.jme3.system.lwjgl.LwjglWindow.run(LwjglWindow.java:632)
	at com.jme3.system.lwjgl.LwjglWindow.create(LwjglWindow.java:466)
	at com.jme3.app.LegacyApplication.start(LegacyApplication.java:463)
	at com.jme3.app.LegacyApplication.start(LegacyApplication.java:424)
	at com.jme3.app.SimpleApplication.start(SimpleApplication.java:127)
	at com.jayfella.jme.vehicle.lemurdemo.MavDemo1.main(MavDemo1.java:226)
Caused by: java.io.IOException: The material parameter: ProbeColor is undefined.
	at com.jme3.material.plugins.J3MLoader.readValueParam(J3MLoader.java:422)
	at com.jme3.material.plugins.J3MLoader.readExtendingMaterialParams(J3MLoader.java:441)
	at com.jme3.material.plugins.J3MLoader.loadFromRoot(J3MLoader.java:771)
	at com.jme3.material.plugins.J3MLoader.load(J3MLoader.java:800)
	at com.jme3.asset.DesktopAssetManager.loadLocatedAsset(DesktopAssetManager.java:260)
	... 23 more


Process finished with exit code 1

removed ProbeColor attribute from the Mountains.j3m & it works but quality is not satisfying :

@yaRnMcDonuts what do you think ?

yaRnMcDonuts · February 22, 2021, 12:49am

That is strange, it appears like the probe is getting scaled to be way too bright, but the textures also looks stretched. I was meaning to run the MAV library myself yesterday to see if I get the same results on my GPU, but did not get a chance

I looked through my own scenes and didn’t notice anything like this, so I will try to run MAV soon and see. If it doesn’t occur with this GPU, then I will also try to run the shaders on my old device to see if I can reproduce the problem there.

yaRnMcDonuts · February 23, 2021, 12:13am

The scene looked normal on this device, so I will give it another look with my other device. I haven’t booted it up in a while, but from past experience, I’ve noticed that there’s a slew of shader errors that this device manages to bypass while the other device will usually catch them.

Also, it sounds like you have managed to load up JME’s PBRLighting.j3md shader without this problem, so the car model in MAV is not causing the same problem is that correct?
And if so, have you also ever been able to use the stock JME terrain with the stock shader called TerrainLighting.j3md?

If the answer is yes to both of these questions, then I can be almost certain that it is indeed a problem in my shader that I should be able to fix.

Pavl_G · February 23, 2021, 8:42am

All the cars are already standard PBRLighting.j3md , as for TerrainLighting.j3md , i havenot tried it before , its better we use a testcase , if we want to reproduce the problem.

yaRnMcDonuts · February 24, 2021, 4:15am

That is a good idea, I actually have this single class test case for a pbr terrain already made that we can use. You can press the ‘p’ key to toggle between triplanar and non-triplanar texturing mode to see if the problem still happens in both modes.

github.com

yaRnMcDonuts/PBR-Terrain/blob/master/examples/TestAfflictedPBRTerrain.java

package com.aaaaGames.pbrTerrain.test;
import com.jme3.app.SimpleApplication;
import com.jme3.asset.TextureKey;
import com.jme3.bounding.BoundingBox;
import com.jme3.bounding.BoundingSphere;
import com.jme3.input.KeyInput;
import com.jme3.input.controls.ActionListener;
import com.jme3.input.controls.KeyTrigger;
import com.jme3.light.DirectionalLight;
import com.jme3.light.LightProbe;
import com.jme3.material.Material;
import com.jme3.math.ColorRGBA;
import com.jme3.math.Vector3f;
import com.jme3.math.Vector4f;
import com.jme3.scene.Node;
import com.jme3.system.AppSettings;
import com.jme3.terrain.geomipmap.TerrainLodControl;
import com.jme3.terrain.geomipmap.TerrainQuad;
import com.jme3.terrain.geomipmap.lodcalc.DistanceLodCalculator;
import com.jme3.terrain.heightmap.AbstractHeightMap;

This file has been truncated. show original

This example is similar to the basic terrain example in the wiki, and uses the same textures from jme3-test-data.

It also uses a light probe that you can find in the same examples directory that the test case above is located in.

sgold · March 8, 2021, 3:08pm

Any news about this issue? @Pavl_G, did you run the single-class test?

Once all known issues are resolved, I’d like to add PBR terrain to JMonkeyEngine. It would be a nice feature to include in v3.4 .

Pavl_G · March 8, 2021, 3:37pm

Exams last 2 more other days & I will be free to try the single test , I am having it in my schedule donot worry .

yaRnMcDonuts · March 8, 2021, 11:57pm

That would be great, I’ll do as much final testing as I can as well, and I’ll also get the advanced test case/example uploaded soon.

I actually finished the test case for AdvancedAfflictedPBRTerrain.j3md, but hit a dilemma in regards to using additional textures as test assets.

My first test case uses the tetxures in jme-test-data, but the second test case will require additional textures for roughness/ao/metallic maps, and also requires that all of the textures are the same size and format to work with a texture array, which is unfortunately not the case for the existent terrain textures in the jme-test-data folder.

So I was wondering if I should just upload my own textures to the PRTerrain test case folder where I also put the light probe for my test case - or would it be preferred that I add these new textures to the jme-test-data library?

I am also curious, if I have access commercially licensed textures from a paid source (such as Substance Source subscription), is it okay for me to include any of those textures in my open source test case as long as I state that the assets aren’t open source/creative commons in a license? Or should I avoid doing that altogether and just find some new textures? IT would be easier to use my current textures so I don’t have to resize and reformat new ones again in preparation for the texture array but I figured I should get some input before going any further with that.