Jump to content


  • Please log in to reply
[10/Linux] Crash when menu would show
3 replies to this topic - Started By holloway, Nov 16 2014 05:10 AM

#1 holloway

holloway
  • Members
  • 32 posts
  • Pip
  • LocationGermany

Posted 16 November 2014 - 05:10 AM

I was pretty excited about the new menu, but sadly I don't come to this point, because it crashes right before it'd show me the menu.

Sun Nov 16 12:06:21 CET 2014 INFO:Slick Build #237
Sun Nov 16 12:06:21 CET 2014 INFO:LWJGL Version: 2.9.1
Sun Nov 16 12:06:21 CET 2014 INFO:OriginalDisplayMode: 2960 x 1050 x 24 @50Hz
Sun Nov 16 12:06:21 CET 2014 INFO:TargetDisplayMode: 1280 x 720 x 0 @0Hz
Sun Nov 16 12:06:22 CET 2014 INFO:Starting display 1280x720
Sun Nov 16 12:06:22 CET 2014 INFO:Use Java PNG Loader = true
Sun Nov 16 12:06:22 CET 2014 INFO:Controllers not available
Sun Nov 16 12:06:22 CET 2014 INFO:Initialising sounds..
Sun Nov 16 12:06:22 CET 2014 INFO:- Sound works
Sun Nov 16 12:06:22 CET 2014 INFO:- 64 OpenAL source available
Sun Nov 16 12:06:22 CET 2014 INFO:- Sounds source generated
saveModule failed to load save file data!
There was an error loading the map!
Sun Nov 16 12:06:34 CET 2014 ERROR:null
java.lang.NullPointerException
        at rpc.map.MapTilesLoader.getTileSetGID(MapTilesLoader.java:517)
        at rpc.map.MapModule.generateBlankMap(MapModule.java:1348)
        at rpc.map.MapModule.loadMapSave(MapModule.java:1375)
        at rpc.map.MapModule.initController(MapModule.java:118)
        at rpc.states.MainMenuState.loadState(MainMenuState.java:142)
        at rpc.states.MainMenuState.enter(MainMenuState.java:192)
        at org.newdawn.slick.state.StateBasedGame.update(StateBasedGame.java:248)
        at org.newdawn.slick.GameContainer.updateAndRender(GameContainer.java:657)
        at org.newdawn.slick.AppGameContainer.gameLoop(AppGameContainer.java:418)
        at org.newdawn.slick.AppGameContainer.start(AppGameContainer.java:328)
        at rpc.launcher.Game.launchGame(Game.java:78)
        at rpc.launcher.Launcher.main(Launcher.java:50)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader.main(JarRsrcLoader.java:58)
Sun Nov 16 12:06:34 CET 2014 ERROR:Game.update() failure - check the game code.
org.newdawn.slick.SlickException: Game.update() failure - check the game code.
        at org.newdawn.slick.GameContainer.updateAndRender(GameContainer.java:669)
        at org.newdawn.slick.AppGameContainer.gameLoop(AppGameContainer.java:418)
        at org.newdawn.slick.AppGameContainer.start(AppGameContainer.java:328)
        at rpc.launcher.Game.launchGame(Game.java:78)
        at rpc.launcher.Launcher.main(Launcher.java:50)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader.main(JarRsrcLoader.java:58)

  • 0

#2 Rayvolution

Rayvolution
  • Developer
  • 1,905 posts
  • Pip
  • Steam ID:Rayvolution
  • LocationTexas

Posted 16 November 2014 - 01:26 PM

Hrm, I found the problem.

 

I'll have a hotfix out soon! ;)


  • 0
Rise to Ruins Developer

#3 Rayvolution

Rayvolution
  • Developer
  • 1,905 posts
  • Pip
  • Steam ID:Rayvolution
  • LocationTexas

Posted 16 November 2014 - 02:11 PM

Hotfix released. The game should work for you now. ;)

 

When you launch, the version number should say InDev 10b, if it does not, restart steam to force it to update.


  • 1
Rise to Ruins Developer

#4 holloway

holloway
  • Members
  • 32 posts
  • Pip
  • LocationGermany

Posted 16 November 2014 - 02:46 PM

Yep, fixed it, thank you. :)


  • 0





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users