sigonasr2/jmonkeyengine
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update MaterialDebugAppState.java

Browse Source 
I was debugging my application to dig down the issue why the shaders are recognized of change but not actually reloaded. I came to this solution.
This commit is contained in:
b00nation 2018-03-08 14:36:23 +01:00 committed by Stephen Gold
parent 9738fc0525
commit 6d5758c914
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
jme3-core/src/main/java/com/jme3/util/MaterialDebugAppState.java
View File

@ -200,7 +200,8 @@ public class MaterialDebugAppState extends AbstractAppState {
assetManager.clearCache(); assetManager.clearCache();
//creating a dummy mat with the mat def of the mat to reload //creating a dummy mat with the mat def of the mat to reload
Material dummy = new Material(mat.getMaterialDef()); // Force the reloading of the asset, otherwise the new shader code will not be applied.
Material dummy = new Material(assetManager, mat.getMaterialDef().getAssetName());
for (MatParam matParam : mat.getParams()) { for (MatParam matParam : mat.getParams()) {
dummy.setParam(matParam.getName(), matParam.getVarType(), matParam.getValue()); dummy.setParam(matParam.getName(), matParam.getVarType(), matParam.getValue());