search

Nanoware / Terasology

Terasology is an open source project started by Benjamin "begla" Glatzel to research procedural terrain generation and efficient rendering techniques in Java using the LWJGL. The engine uses a block-based voxel-like approach as seen in Minecraft. After proving itself as a solid tech demo begla was joined at first by Anton "small-jeeper" Kireev and Rasmus "Cervator" Praestholm and a full-fledged game concept was born. Our goal is a game that pays ample tribute to Minecraft in initial look and origin, but stakes out its own niche by adopting the NPC-helper and caretaker feel from such games as Dwarf Fortress and Dungeon Keeper, while striving for added depth and sophistication in the foundation systems akin to DF.
http://terasology.org/
Apache License 2.0
4 stars 1 forks source link

AssetManager cannot resolve Core module content in eclipse #57

Closed msteiger closed 11 years ago

msteiger commented 11 years ago

NOTE: This issue is probably not a bug - it seems to be related to the eclipse (classpath?) setup - it works when using gradle directly.

I get this when starting a new game:

Unable to instantiate unknown prefab: "core:railgunTool"

I traced it back to AssetManager which has only "engine" as asset source type. I assume that the Core module must be somehow registered there by the ModuleManager. Any ideas how to fix this?

Cervator commented 11 years ago

The Core module is outright configured as a sub-project (IntelliJ module) via Gradle. Could a dependency on it be missing when trying to run via Eclipse?

It might also be that starting from Eclipse leaves you with a different working directory than IntelliJ / command line. If you look in the constructor for PathManager there are some tweaks there depending on how the game is started. Should be logging some paths too on startup.

msteiger commented 11 years ago

Good guess! I was the problem as in #56 - changing the working directory to the TS root folder fixed it.