Search results

Great! Thanks! :-)

Bump - got working Distros in Jenkins. Now the question is exactly how we want to organize that stuff, especially for the launcher, and how to change reading needed info as that's in multiple jobs now http://jenkins.terasology.org/view/Nanoware/job/NanoTerasology/ - engine build job that makes...

Also posting about the "spawn in depression" tendency, just came up with three of us on IRC, heh :-) Maybe could help / be related: https://github.com/MovingBlocks/Terasology/issues/1379

That delta is pretty weird, actually. 22:59:24.210 [main] INFO o.terasology.engine.TerasologyEngine - Initialization completed in 5.93sec. 22:59:25.262 [main] WARN o.t.engine.internal.TimeBase - Delta too great (189424806), capping to 1000 22:59:26.615 [main] INFO...

If you want to try lower graphic settings (and yeah I figure with it being the menu it wouldn't matter) you can try just replacing all the "true" entries with "false" in the "rendering" section. That gets most of them. Saturday we have a couple office hour blocks, the early one starts one hour...

Hmm, tricky! Still not a whole lot to go on :-) Maybe we need to get you a debug build with some more logging enabled. Perhaps if you have some time over the weekend you could hop on IRC to talk with us live? What time zone are you in and are any times of day better for you?

Welcome @timagn ! Thank you for the kind words :) Am much in agreement with your egg analogy, as we have much more architecture at this point than content. You can build all kinds of things on top! I like your reference to Master of Magic as I hope to see larger world features like that in...

Hi @Love_Craft and thanks for checking in :-) Hmm, the logs looks pretty decent, your system is a laptop I take it, with an ATI Mobility Radeon HD 5470. Being from 2010 that's not too old and it beats the usual Intel graphics in any case. You run the game and the main menu loads but gives you a...

Curiously, just for notification with builds and such, would that be a world breaking change? Not that there are a lot of worlds to break, so now would be the time :-)

We're not quite ready, but I believe we are very close :-) I did some analysis on the topic a little time back, and just now crossed out half the top priority issues (had to install a Xenforo addon real quick to bring back strike-through, heh), with the remaining ones being smaller. Lots more...

Thanks for the pointer - forwarded it to our little group at work since that's where the Windows magic is needed :)

Here's a likely relevant bug issue: https://github.com/MovingBlocks/Terasology/issues/1316 Probably we can harden BlockPicker to discard invalid blocks somehow. Maybe we can load them in a more basic way when just for show, simply ignoring the prefab definition entirely? That could also avoid...

Walking off edges - that should IMHO be included in crouch/sneak like in other games (like MC). Normal walking/running will go off edges all day long, but start moving carefully/sneaky and you'll stick on edges. Page up/down - I'd save those for scrolling in chat / console / UI screens...

Here's the latest BlockPicker build: http://jenkins.terasology.org/view/Modules/job/BlockPicker/lastSuccessfulBuild/artifact/build/libs/BlockPicker-0.1.0-SNAPSHOT.jar Download that jar and put it into the modules directory (be sure to delete the old BlockPicker) That dir should be in your user...

Scope: Engine feature Code: Engine repo Wiki doc: Engine - Input Bindings Issue tracker: Engine Ideas / todo: Trello Curator: Needed Our approach to input bindings so far has pretty much been finding a single new key when we need one. I think it is about time we get more organized on strategy...

I went ahead and cleaned out a pile of old engine builds in Jenkins. I've got a local backup anyway should we want to put up a historical archive some time for the fun of it. Engine builds went from 40 minutes (due to memory/cpu thrashing) back down to 9 minutes :-) Almost upgraded to the next...

Thanks for the catch, yep - corrected :D

Yes, Windows 8 sucks :D

No stable build post this time, just a quick note that a first round of Jenkins / Gradle / Artifactory / Release related changes have been merged. This is part of the logistics arc to finally doing a proper release management approach with SemVer-based versioning. It means a few things: Latest...

Merged the changes :-) Seems pretty stable and I've bumped up the version so the older artifacts won't get picked for resolution. Goes with our existing stable build numbering (in the minor position just because) until we do something different (SemVer isn't in full effect for major release 0)...