Hi Shore. I like your demo very much. The water effects are great. The models are all great. I like the effect if one gets hurt by a wasp.

Your scripting is very good!

I had no problems with fighting the enemies (running around them and beat them from side or from behind) but I did that with the fist because I did not know how to find the weapons in the inventory.

Besides that I could not find a map to find my way through the level. So I could not find any person to get a quest or something like that. Yes I know you have created a map in your manual but it would be nice to see that in the game.

I think that the night is too dark. I could not play it then.

I would really play that superb game when it is finished and improved. You have much more experience with 3dgs than me. I admire that.

Frank

Switching to XP solved a lot of crashes and other problems in my case. I did not experience any crash in XP with a proper hardware. I think it was worth the money.

Frank

I don't see a reason to wreck my system. It's perfectly configured an running fine.
I also have doubts whether this problem is a win98 issue, I've read about this error message before, and the user with the problem had win xp.

Another idea just came to my mind. In my BIOS settings I've reserved 64 MB Ram for the video card, maybe that is causing problems.

Sorry, I did not intend to turn this thread into a win98 vs. win xp discussion.

Hi Frank_G!

First of all: You have to pick up a weapon, otherwise there will be no weapon ring!
The first one lies beside you and the others are on the table at the wooden stairs.

But as I see, you figured out how to fight them well!

The NPC thing:
I'm short of models. You have to look for moedls having the shape "NPC" read from the top to the bottom.
The first one is outside the fisher's house northeast from the starting point.
(he'll tell you where to go next)

Night already was menitoned, I'll fix...


This morning I found out some little bugs:
Empty pointer when wealding a shield and switching to the bow. (silly me, was a stupit mistake)
Empty pointer when wering bow or claw and entering the status menu. (didn't watched closely after the last changes)
And the background in satus and skill menus is totally black but should only be darkened, I hadn't set back the alpha to 50% after the splashscreen.

yep the server seems to be back, downloading now.

Not sure if it is of interest, if not, pleaseignore this post:

I perhaps have found the reason for the message above.
The terrain demo posted somewhere here in showcase also shows this error message. I took a look into the files (it is not resourced) and saw it's using a terrain with shader applied. Not sure if the shader is a problem, as everything ello released is running, but it might have to do with the terran.

The campground demo presented a while ago, features terrain without shader and ran without any problem.

Too bad that I can't see the nexus/video memory values of the demos, it might help to get an idea what is wrong with my (and some other) system(s). Maybe it indeed is a driver issue, I don't know, but I doubt that the demos mentioned are using more than 64MB video memory..

I'm using a terrain shader as well....

I had to set the Level's Nexus to 400, don't ask me why but otherwise publish crashed. I guess it is because publish doesn't watch for script settings where I set max. entites to 2.000.

The Nexus is at 400?

This explains why it doesn't run on my system. I don't know what takes so much memory with my setup, but even after closing firewall and antivir still over 100 MB are in use... so I end up with about 400MB free ram, which doesn't seem to be enough.

I also had a problem with max entities exceeded. The limit is increased with increasing nexus, but it can also be raised manually: max_entities (I guess this it what you tried first?)

Haven't tried publishing, as I always use resource, but maybe this indeed is an engine problem.

The problem is, that there are many entites in the map (espacially trees and gras).
With max_enities = 2000 there is no problem in runtime, but as said before, publish doesn't look at the script and just sees, that there are much more entitys in the map as the nexus would allow and crashes WED.

Maybe 400 was a bit to much, I just doubled it as I recognized it was the problem (don't ask me, why I came to the stupid idea this was the problem) and then it worked.

But newertheless I have the similar RAM sizes as you got... really strange.

I'll try with a bit lower nexus in the next version, so I hope that'll fix it...