Guppy

Hopefully the "assert failed" has a bit more information than that, the assert macro basically means "make sure that x is true, if not then die"

Ideally it should have placeholders for the non-free you dont have so you can actually load a map

That is very cool!

While that is nifty I was aiming for encrypted containers, dont suppose I can teach package new tricks?

This, very much this. Though I'd also like to somehow be able to extend the built in classes either by replacing them entirely or some kind of hook system. Not all of us are unwashed religious nut jobs like stallman!

Bumping this hoping for an answer in time for the c++ release Bascially what I want is to create a class VirtualFileSystem:FileSystem http://www.leadwerks.com/werkspace/page/documentation/_/command-reference/filesystem/ And then force leadwerks to use that instead

As for competitors stealing the source code, UDK4 has full sourcecode on git hub for $10 - so clearly that's one company that thinks the potential feed back outweighs the risk of theft

You can also just use blender https://www.youtube.com/results?search_query=blender%20sapling%20tutorial&sm=12

You must be new to linux, the major reason people switch distros is for technical differences - such as default/supported DE, package system and release method. Usually the first reason they switch is the DE - having seen somebody else using something different they liked or simply having too much trouble adjusting to their current. As for the whole "omg the software I'm using is dying" - that's the beauty of opensource, you can simply buckle up and maintain it your self ( or use money to make somebody else interested in doing it ). (and yes you can make money off of opensource, there are plenty of companies doing this - hell my dayjob is working for such a company )

Josh *hopes* to have it out soon, barring anything unforeseen - should something like that happen he will push back the date ( as has already happened, it was originally planned for Dec 2013 ). So to answer the question; There is no release date set, it will be released when Josh feels it's of a quality ready to release - or more succinctly "When is done" Which has become somewhat of a motto for a large software developer.

When it's donetm

The difference lies in that Josh is closer to the process than normally, a lot of bumps and bruises the is perhaps really easy to smooth out is normally not reported ( automating workflow, etc ). So what's in it for the different parties? Josh/Leadwerks: Shiny new promotional material; production blogs, and a simple ready made game licensees can pick apart and study - also the game it self if released on steam or the like could attract new developers. The team: Self promotion, more direct developer contact and pushing your issues to the front Already in this tread something has been uncovered that may not have been thought of before - how do you share a project between multiple parties, other than having a project lead that merges everything manually I don't see a way, so clearly here is some room for improvement. at any rate it's just an idea

based on the code you posted Im guessing that 'Script.position' is nil - it refers to "self.model" which isn't set in the code snippet you posted also function App:Joint(parent_position, child, parent) joint = Joint:Ball(self.parent_position, self.child, self.parent) end Assuming that lua is like most other OOPs "self" is a pointer to the object instance meaning that self.child != child meaning that you call Join:Ball with (nil,nil,nil) that seems likely to cause a crash even if self.model is defined

Inspired by this update by the user "marcus" I had an idea. Development of new features in blender is driven mostly by the openmovie projects ( http://www.blender.org/features/projects/ ) the advantage of this approach is that blender gets new features that are not only needed but thoroughly tested and works in a way that makes sense to the users - thus sidestepping the flaws usually associated with interaction designed by programmers . I wonder if it would not be worth doing something similar for leadwerks. The basic idea being you select a group of leadwerks developers who knows their way around the engine / have shown published something with it ( henceforth "the team" ). The team will then decided upon a project eg. a RTS game, and then report any problems or shortcomings in the workflow and/or engine. The leadwerk developer(s) will be monitoring on the sidelines fixing problems as they occur and helping integrate patches. Two problems I see with this is that LE being closed source I don't think the team will be able to contribute much in the way of code, and secondly I think there is only one LE developer which could turn out to be a bottle neck. I'd love to hear what you think about this suggestion, even if you just think it's a horrible idea ( but do be specific about the why )

Ogre3D (not a game engine) had it for a while - it looks very good, especially the eyes http://www.ogre3d.org/forums/viewtopic.php?f=11&t=73261

Thats for private betas - the public beta should be available

http://www.linuxliveusb.com Start there

If you just want an extended try without repartitioning tour hård drive I reccomend going with a live usb

Holy necro batman! Any reason You decided to resurect a 2½ year old thread?

just install gimp and it should preload all the gnome/gtk+ packages your missing

You can use raknet or any shared library in lua but you will need to make a wrapper that exports the functionality to lua

same thing for linux; xargs -a filelist.txt -d '\n' rm

While I certainly believe any aspiring game programmer should atleast know the basics of assert creation it's not always needed; http://www.leadwerks.com/werkspace/topic/8507-free-resources/ (also some texture resources there) So unless you have a very specific art direction you may be able to cut a few corners.

Reminds me og orcs must die that last one. Nice work

To sum up the 5 pages : you just need to find some spherical cow that can live in a vacum!