jMonkeyPlatform Alpha-4 Niightly Build Has Compile Errors

Troubleshooting SDK
1

Greetings,

I am using jMonkeyPlatform Alpha-4 Nightly Build Version: 0.6.0.7365. I updated it today through the update program. After the restart of the IDE, I get the following errors as shown in the screenshot.





Also notice that many of the JME tests are broken too.

Did I do something incorrectly when updating?

Thanks

2

Looks like you’re on some Linux distribution. Unfortunately jMonkeyPlatform is having a lot of issues on Linux lately. The developers are looking into it though.

3

@erlend_sh Yep. I am using Ubuntu 10.10 with 2.6.35 kernel. The reason I switched from stable to nightly build is that I was having lockups when trying to use the SceneComposer (adding lights and effects would cause this behavior).



Is there any information I can provide to assist - log files and such?

4

Also, how is it possible that there are errors in the JME test projects?



For instance in TestCameraMotionPath.java the com.jme3.cinematic.MotionTrack library can’t be found.

5

nightly == unstable, its normal that a nightly version might be broken at some point

6

Hi to all,



I am also having problems with the update on jMonkeyPlatform.

It seems I cannot open any of my previous scenes.



Thanks

7

What’s the problem? I mean you should have an error

8

Yeah , I also get that issue too… After update through Nighty Build (hell!) => Now the SceneComposer and the Nifty GUI Editor is broken :



Open a scene or j3o file:



java.lang.UnsupportedOperationException: You cannot delete from the smart cache

at com.jme3.asset.AssetCache.deleteFromCache(AssetCache.java:88)

at com.jme3.asset.DesktopAssetManager.deleteFromCache(DesktopAssetManager.java:165)

[catch] at com.jme3.gde.core.assets.SpatialAssetDataObject.loadAsset(SpatialAssetDataObject.java:80)

at com.jme3.gde.scenecomposer.OpenSceneComposer$1.run(OpenSceneComposer.java:44)

at java.lang.Thread.run(Thread.java:619)



Open A nifty file

java.lang.NullPointerException

at de.lessvoid.nifty.Nifty.displayResolutionChanged(Nifty.java:685)

at de.lessvoid.nifty.Nifty.render(Nifty.java:270)

at com.jme3.gde.gui.multiview.NiftyJmeDisplay.postQueue(NiftyJmeDisplay.java:128)

at com.jme3.renderer.RenderManager.renderViewPort(RenderManager.java:1121)

at com.jme3.renderer.RenderManager.render(RenderManager.java:1159)

[catch] at com.jme3.gde.core.scene.SceneApplication.update(SceneApplication.java:238)

at com.jme3.system.lwjgl.LwjglAbstractDisplay.runLoop(LwjglAbstractDisplay.java:144)

at com.jme3.system.lwjgl.LwjglCanvas.runLoop(LwjglCanvas.java:199)

at com.jme3.system.lwjgl.LwjglAbstractDisplay.run(LwjglAbstractDisplay.java:218)

at java.lang.Thread.run(Thread.java:619)

com.jme3.asset.AssetNotFoundException: aurulent-sans-17.fnt

at com.jme3.asset.DesktopAssetManager.loadAsset(DesktopAssetManager.java:236)

at com.jme3.asset.DesktopAssetManager.loadFont(DesktopAssetManager.java:339)

at com.jme3.niftygui.RenderFontJme.(RenderFontJme.java:54)

at com.jme3.niftygui.RenderDeviceJme.createFont(RenderDeviceJme.java:116)

at de.lessvoid.nifty.render.NiftyRenderEngineImpl.createFont(NiftyRenderEngineImpl.java:176)

at de.lessvoid.nifty.loaderv2.types.apply.Convert.font(Convert.java:35)

at de.lessvoid.nifty.loaderv2.types.apply.ApplyRenderText.apply(ApplyRenderText.java:23)

at de.lessvoid.nifty.elements.Element.initializeFromAttributes(Element.java:319)

at de.lessvoid.nifty.loaderv2.types.ElementType.applyAttributes(ElementType.java:218)

at de.lessvoid.nifty.loaderv2.types.ElementType.applyStandard(ElementType.java:172)

at de.lessvoid.nifty.loaderv2.types.ElementType.create(ElementType.java:144)

at de.lessvoid.nifty.loaderv2.types.ElementType.applyChildren(ElementType.java:251)

at de.lessvoid.nifty.loaderv2.types.ElementType.applyStandard(ElementType.java:175)

at de.lessvoid.nifty.loaderv2.types.ElementType.create(ElementType.java:144)

at de.lessvoid.nifty.loaderv2.types.ElementType.applyChildren(ElementType.java:251)

at de.lessvoid.nifty.loaderv2.types.ElementType.applyStandard(ElementType.java:175)

at de.lessvoid.nifty.loaderv2.types.ElementType.create(ElementType.java:144)

at de.lessvoid.nifty.loaderv2.types.ScreenType.create(ScreenType.java:80)

at de.lessvoid.nifty.loaderv2.types.NiftyType.create(NiftyType.java:137)

at de.lessvoid.nifty.Nifty.loadFromFile(Nifty.java:507)

at de.lessvoid.nifty.Nifty.fromXml(Nifty.java:392)

at com.jme3.gde.gui.multiview.NiftyPreviewPanel$2.call(NiftyPreviewPanel.java:132)

at com.jme3.app.AppTask.invoke(AppTask.java:147)

at com.jme3.app.Application.update(Application.java:558)

at com.jme3.gde.core.scene.SceneApplication.update(SceneApplication.java:220)

at com.jme3.system.lwjgl.LwjglAbstractDisplay.runLoop(LwjglAbstractDisplay.java:144)

at com.jme3.system.lwjgl.LwjglCanvas.runLoop(LwjglCanvas.java:199)

at com.jme3.system.lwjgl.LwjglAbstractDisplay.run(LwjglAbstractDisplay.java:218)

at java.lang.Thread.run(Thread.java:619)

9

That NullPointerException is a nifty gui issue since it happens inside nifty gui code. The j3o issue happens because jMP removes an asset from the smart cache which is not allowed

10

The first issue should be fixed in next nightly

11

I’ve just return it back to the last stable update by uninstall all the JME core plugins and then download them all again (with the nightly build source unchecked). It solve all the probs … Some thing in the nightly update make the plugins broken !

12

@nehon : that’s fast ! :[

13

It was fixed wrong, we need to re-add deleteFromCache() since the data in the file could have changed through editors etc. Hope you remember where you removed those calls :stuck_out_tongue:

14
atomix said:
@nehon : that's fast ! :[

yes ...but because
normen said:
It was fixed wrong,


:D

@Normen yes i remember i just commented the line throwing the exception.

The thing is, we can't delete from smartcache...that's a bit above my head, so I guess you'll have to discuss this with Kiril
15

Yes we can

16
Momoko_Fan said:
Yes we can

^--- result of the discussion with Kirill xD
17

good :smiley:

18

Hi,



when should this “Error in scene!” issue be fixed? I’m facing exactly the same problem after the nightly build update 2 minutes ago…

Is there a workaround? Unfortunately I can’t do anything…



Kind regards,

Stefan

19

@shadow82 Yep. I also can’t do anything with the nightly build and the stable doesn’t work for me either as shown in the following clip:

http://www.youtube.com/watch?v=QJB2EXM2hFs

20

Exactly my problem, stable version freezes… thats why I updated to nightly build.