No problem what so ever , done everything and no crashes

Radeon 4770
Athlon X2 6000
4 Gig Ram
Win 7
GS 7.82

Current Gamestudio edition: A7.82.3 (Pro)
My System Specs: Windows XP Home Edition Version 2002 Service Pack 3
RAM size: 2,0GB
# of processors: 2 @ 2,0GHz
gfx card type: NVIDIA GeForce Go 7900 GTX @ 512MB
DirectX 9.0c

Open Backyard.wmp from WED and run it. Does it compile? Yes. Does it crash? No. [...]
Open a heavy application. It could be Photoshop. With this application open, run the level from WED again. Does it crash? No.
Finally, open main.c from SED. Run the blue arrow (Run current Script). Does it compile? Yes. Does it crash? No.

Tested with Nexus from 30 to 300.

I will perform your tests on two of my computers at home when I get the chance.

BTW, when I try to follow your "If you have the latest A7.83.6b then don't test this at all since you'll get a lot of errors. Check this thread for more on this)" link, I get "Access denied."

@Pighunter: you need to be a pro user with beta forum access

it doesnot crash when running from wed or sed.

I didn't get crashes using WED or SED.
The only thing which is to mention is that if i open the wmp file I get a message that it can't open IntensX.h

System
Windows Xp 23bit Home
intel Core2 Quad Q8200 2.33GHz
Nvidia 260 GTS260
3.25GB RAM

3.82 Free decals dissabled

muffel

I don't think you must worry about your reputation; everyone realizes that indipendent efforts are challenging.

Disabled decals in dat file:

Version
7.82.3 Extra


Machine specs:
1GB Ram
Win Xp SP3
82845G Integrated Intel GPU
Dell
P4 2.66

First Run:
Sed:
Worked fine after decals set to 0 for Extra

Second Run:
Wed:
loading into wed error "Can't load intensex.h"
Compiled in a few mins and ran without engine error.

Third Run:
Sed:
Error after a few seconds of play:
Error E1201
Nexus too small (0)

Fourth Run:
Sed:
Same error:
Error E1201
Nexus too small (0)

Fifth Run:
Sed:
same as last two

Sixth Run:
Wed:
3 Browser Windows open:
loading into wed error "Can't load intensex.h"
Run fine

Seventh Run:
Wed:
Photoshop Running
Demo ran fine with photoshop in background.

(Would ensure that non player characters are optimized with LODs for low end PCs.)

Looks cool, keep at it. You'll get it worked out.

Good morning Larry,

I did some quick checks on your code and I'm pretty sure what causes the problem (not that you're able to solve it, but at least it should be a good hint for jcl).

Started your level from WED and it crashed - as you said.
Started the level from SED and it worked perfect.

==> Checked the different parameters for the engine with -diag.
Paramters when running from WED: -nx 300 -diag -wnd
Parameters when running from SED: -diag -wnd -ta -debug

==> Removed -debug & -ta from the command line / did not change anything
==> Added -nx 300 to the command line ==> crash
==> Removed -nx 300 from the WED commandline ==> no crash

The -nx statement for its own does not cause the crash (-nx40 is working smoothly) - but it seems as if the high value leads to the crash.

As the error seems to happend randomly on different computer-settings I would suggest you to check if the crash is in relation to the height of the nexus value (e.g. if it doesn't crash, just set a value like -nx 1200 ).

Greetings,
Timo Stark

PS: just saw that this problem was already reported - so it might be the magical number 300 aaand
PS2: pretty amazing, but it don't seem to stand in any relationship to the available memory

System specs:
Windows XP (SP3)
Genuine Intel CPU 585, 2.16 GHZ
2 GB ram
Mobile Intel (R) 4 Series Express Chipset Family (yeah integrated gpus rocks )

But what can be stated is, that this is an engine bug,
not a bug in the application programming.
It runs on some systems and crashes on others, with
the engine beeing responsible for the management.

So its (as discussed before) Conitecs turn to fix that!

How about a developer planning with a large project reads
on the product page:

"For large projects, the game might crash on some systems.
Its your not our responsibility to fix that."