Another Update and more things are broken

macklebee · **Posted:** Tue Nov 10, 2009 3:46 am

and like I said before... without more information like providing an example program with a terrain that shows this issue you might as well just not even complain. How can anyone, even Josh, attempt to troubleshoot anything without at least an example? This is a perfect example of an Incomplete Bug Report. Take the time to make a small example and others might be willing to help more.

darrenc182 · **Joined:** Sun Jul 13, 2008 7:00 pm **Posts:** 113

Alright I found out the problem was the phy file from the problematic model was no longer valid for the updated version of 2.28 (remember I just updated from an earlier version of 2.28). Well I'll need to change all of the other phy files for the scene to see if that stops Sandbox from crashing.

Marleys Ghost · **Posted:** Tue Nov 10, 2009 9:56 am

darrenc182 wrote:

Rick wrote:

Note that you will pay $50 more for 2.3 according to Josh. Small price to pay for the tool but a cost all the same.

I want to see 2.2x stable with all features working 100% before I can even consider paying $50 for 2.3. That means no more falling through terrain, which I think has been a problem since 2.24, at least for some of us.

Here is my log from Sandbox.

H:/Leadwerks/Leadwerks Engine 2.28

Leadwerks Engine 2.27

Which version are you actually using?

Lumooja · **Posted:** Tue Nov 10, 2009 10:28 am

Falling through terrain happens also in commercial games, and they usually fix it by moving the player back on the surface when he is below the terrainheight at his x,y position.

eternalcrisis · **Posted:** Tue Nov 10, 2009 10:44 am

Lumooja wrote:

Falling through terrain happens also in commercial games, and they usually fix it by moving the player back on the surface when he is below the terrainheight at his x,y position.

I've seen this a lot in games using the Gamebyro engine.

DJDD · **Joined:** Mon Aug 31, 2009 10:53 am **Posts:** 52

Lumooja wrote:

Falling through terrain happens also in commercial games, and they usually fix it by moving the player back on the surface when he is below the terrainheight at his x,y position.

That reminds me of a story I read on Gamasutra - A team was trying to move the game from console->PC (or the other way around) and for whatever reason the levels completely broke open with seams everywhere. They spent WEEKS doing QA and patching em through testing but could never beat it. So a programmer basically wrote like 2 lines of code:
If(player.posZ <= 0)
move(player, Vec(player.posX, player.posY, player.lastPosZ));

Such dirty hackery, but so effective! I laughed.

Lumooja · **Posted:** Tue Nov 10, 2009 11:02 am

When finishing games, you always end up with some hacks. There is no engine which would 100% work for all games in all situations, but as long you can hack around it, it's fine.

DJDD · **Joined:** Mon Aug 31, 2009 10:53 am **Posts:** 52

Lumooja wrote:

When finishing games, you always end up with some hacks. There is no engine which would 100% work for all games in all situations, but as long you can hack around it, it's fine.

Aye, well I guess that when you're in business you make your choices based on what will get you to your end-goal in the best way. That hackery was the answer.

darrenc182 · **Joined:** Sun Jul 13, 2008 7:00 pm **Posts:** 113

Marleys Ghost wrote:

darrenc182 wrote:

Rick wrote:

Note that you will pay $50 more for 2.3 according to Josh. Small price to pay for the tool but a cost all the same.

I want to see 2.2x stable with all features working 100% before I can even consider paying $50 for 2.3. That means no more falling through terrain, which I think has been a problem since 2.24, at least for some of us.

Here is my log from Sandbox.

H:/Leadwerks/Leadwerks Engine 2.28

Leadwerks Engine 2.27

Which version are you actually using?

I thought I was using 2.28, but I guess with that update it reverted back to 2.27, which is why it had problems with the phy files. I am now using LE 2.28.

Naughty Alien · **Joined:** Sun Feb 08, 2009 2:40 pm **Posts:** 301

..im using 2.23 for my game and never ever had any issue with phy files at all..

darrenc182 · **Joined:** Sun Jul 13, 2008 7:00 pm **Posts:** 113

Lumooja wrote:

When finishing games, you always end up with some hacks. There is no engine which would 100% work for all games in all situations, but as long you can hack around it, it's fine.

Yeah that's great and all, but I don't have the access I need to create a hack for the falling through terrain problem. If I had the full source then I might be able to create a hack, but I can't.

On a separate note, was there ever a version of Framewerk released for version 2.23? If so I am going to follow Naughty Alien and go back to using v2.23.

gameproducer · **Posted:** Mon Nov 23, 2009 7:19 pm

Quote:

On a separate note, was there ever a version of Framewerk released for version 2.23? If so I am going to follow Naughty Alien and go back to using v2.23.

Well, this would be nice... if one could do it. But apparently for example I have a version that I intend to release (needs only more content: map work and stuff like that - no extra features any more). In 2.24 the demo runs okay, except that shadows don't work if you have newest drivers.

I got informed to upgrade to newer... which I'm doing... but with the new version I cannot see any meshes and controller goes crazy.

I'm sniffing around the forum and trying to get things right. But... if you don't upgrade, then the game won't work on new nvidia drivers and on many ATI cards. But if you upgrade, a quest for holy update problem info begins.

Of course it's understandable since this engine is going through major development/changes, but the bottom line is that one cannot release stuff to public using 2.24 - since it won't run properly with the newest drivers.