kennar

Rick: Makes sense however the research/simulation world is a blend where individual projects as defined stand a greater chance of completion. With respect to school children or the military applications the constructed scenarios are effectively game-like, minus the full story. Let's rephrase and suggest that skills could be "leveraged" while still working games. These worlds are not mutually exclusive. My assumption is that most here would like to remain in the gaming marketplace knowing that income must be supplemented. I wasn't really suggesting that folks switch streams rather the key point was that a product like LE serves multiple overlapping markets consequently design choices must take these into consideration.

Triggered by the current thread “Supporting Game Development” let me comment from the perspective of a non-game developer or even player. As noted by one of the respondents, the obvious for a game engine is to include the current market expected API. That is, some of the obvious elements, rain as mentioned, should not be excluded and should be placed on a forecast list. Understandably Leadwerks is a work in progress with a fairly attentive proprietor consequently the base can reasonably expect gaps to be filled as version numbers climb. In the interim, it is essential to make clear what is present to the novice users - those just testing the waters. Everyone is a potential client. Now, from my perspective I do have an interest in games but from a vantage point informed by research in cognition, perception, or simply neuroscience these days. Much has been learned about the limitations of how we cognitively respond to the environment - both in the lab and real world. Some of these effects can be a hindrance in critical if not life threatening situations. Others if exploited in a game world fit nicely into the mental fitness market. Overall, there is a open question of integration into game play. If doable, obvious target markets include both the very young and elderly. Outside of that box are athletes and the military. A large subset of such products are not necessarily for the mass market, meaning it may be worth considering that application frameworks (e.g., QT, wxWindows, IUP, ...) do in fact overlap with Leadwerks for the purpose of blending the professional with game play or simulations. The focus on gaming GUIs (e.g., CeGUI) is at times a limiting factor when it comes to the look and feel of a commercial quality research tool. --- That’s the little bee in my bonnet. Essentially, the core of LE could be more than just suitable for what is considered traditional gaming. It doesn’t have to just be lip-service. In fact, what is described above requires a far shorter developmental cycle than the numerous gaming projects announced on pages such as these. Indeed, many here have the skill to capitalize on that often hidden market. An incomplete thought that I hope suggests more for the LE.

Thank you. That's a very big step from this perspective.

By way of introduction, I acquired LE2.32 in December but because of work and an ongoing project I have spent essentially no time with the Editor and API since then, consequently this domain is still very new despite regularly visiting the forums. It get's worse; I'm actually not a game player of any kind. Sacrilege? Even so, LE is extremely enticing for basic simulations while incorporating gaming and testing elements into small applications. This blog, will serve as spot for me to post what are undoubtedly novice hurdles. If answers/hints/direction magically appear in the comments that would be very cool. Hurdle #1 Having just acquired 3rd party models (e.g., Shanty Town from Arteria3D) I'm at a loss for how to create the physics files. Dragging objects produces the *.phy files however the properties are blank. The same applies when using phygen and obj2phy. My expectation was that switching into "game mode" in the editor would introduce collision detection for those newly added objects. K.