newest trunk build - problem...

[lav_coyote25]

wz2100_shot_001.png

using the build from the newest installer - all the old non new renderer is used...

using the trunk exe uploaded most recent - see the pic.

ok!! whats up. xD

[Buginator]

What map is that?

If you are using warzone2100r7789.exe on trunk, then it should be working OK. At least, it works on my end...

You getting anything in stderr.txt or anything?

[lav_coyote25]

map is reull - one of mine - worked on the old trunk prior to this one... so dont know why it would all of a sudden not work...

this is the stderr.txt file... no other error rpt or anything. just the following 900 k or so of error: blah blah blah.... xD xD

stderr.txt

[lav_coyote25]

here is what it should look like... reull with trunk version r7535

wz2100_shot_679.png

[lav_coyote25]

and this is what the new release looks like without the new render engine....

wz2100_shot_680.png

[lav_coyote25]

now i get this?? after a little into 1 hour.... see pic.

Code: Select all

error   |01:07:19: [interpRunScript] interpRunScript: max instruction count exceeded - infinite loop ?
error   |01:07:19: [interpRunScript] interpRunScript: *** ERROR EXIT *** (CurEvent=30)
error   |01:07:19: [interpRunScript] Original event ID: 110 (of 117)
error   |01:07:19: [interpRunScript] Current event ID: 30 (of 117)
error   |01:07:19: [interpRunScript] Call depth : 4
error   |01:07:19: [scrOutputCallTrace]  *** Script call trace: ***
error   |01:07:19: [scrOutputCallTrace] 4: N/A (current event)
error   |01:07:19: [scrOutputCallTrace] 3: N/A (return address: 035A58B0)
error   |01:07:19: [scrOutputCallTrace] 2: N/A (return address: 035A5D50)
error   |01:07:19: [scrOutputCallTrace] 1: N/A (return address: 035A5AF8)
error   |01:07:19: [scrOutputCallTrace] 0: N/A (return address: 035B1210)
error   |01:07:19: [interpRunScript] interpRunScript: error while executing a script
error   |01:07:19: [interpRunScript] Assert in Warzone: interpreter.c:946 (!"error while executing a script"), last script event: 'N/A'
error   |01:07:19: [eventFireTrigger] eventFireTrigger: event N/A: code failed
error   |01:07:19: [eventFireTrigger] Assert in Warzone: event.c:1128 (0), last script event: 'N/A'
error   |01:07:19: [stackReset] stackReset: stack is not empty
error   |01:07:19: [stackReset] Assert in Warzone: stack.c:1048 (((psCurrChunk == psStackBase) && (currEntry == 0))), last script event: 'N/A'
error   |01:08:27: [interpRunScript] interpRunScript: max instruction count exceeded - infinite loop ?
error   |01:08:27: [interpRunScript] interpRunScript: *** ERROR EXIT *** (CurEvent=49)
error   |01:08:27: [interpRunScript] Original event ID: 110 (of 117)
error   |01:08:27: [interpRunScript] Current event ID: 49 (of 117)
error   |01:08:27: [interpRunScript] Call depth : 2
error   |01:08:27: [scrOutputCallTrace]  *** Script call trace: ***
error   |01:08:27: [scrOutputCallTrace] 2: N/A (current event)
error   |01:08:27: [scrOutputCallTrace] 1: N/A (return address: 035A5AF8)
error   |01:08:27: [scrOutputCallTrace] 0: N/A (return address: 035B1210)
error   |01:08:27: [interpRunScript] interpRunScript: error while executing a script
error   |01:08:27: [interpRunScript] Assert in Warzone: interpreter.c:946 (!"error while executing a script"), last script event: 'N/A'
error   |01:08:27: [eventFireTrigger] eventFireTrigger: event N/A: code failed
error   |01:08:27: [eventFireTrigger] Assert in Warzone: event.c:1128 (0), last script event: 'N/A'
error   |01:08:27: [stackReset] stackReset: stack is not empty
error   |01:08:27: [stackReset] Assert in Warzone: stack.c:1048 (((psCurrChunk == psStackBase) && (currEntry == 0))), last script event: 'N/A'

wz2100_shot_682.png

[lav_coyote25]

ok... is anyone working on the above problem? if not let me know please... and i wont waste anymore time testing it.

[Per]

What is wrong in that picture?

[lav_coyote25]

look at the top pic... then the next in line...etc...

[Zarel]

What is wrong in that picture?

Only the top pic (with no terrain) is the problem. The other ones are just for comparison.

[lav_coyote25]

so has this been fixed????????????????????????????????????

[Per]

Script errors are really hard to debug, no-one is really touching those. I think everyone is just waiting for the lua branch to be done.

As for the terrain problems, better ask gerard when he gets back if he can trace the changes between those two versions to see what changes might have caused those.

[Buginator]

ok... is anyone working on the above problem? if not let me know please... and i wont waste anymore time testing it.

The lack of textures (white area) is almost always a driver issue.
Update your gfx drivers.

As for if anyone is working on any of this, everyone is busy, so little is being done right now, but that don't mean we won't come back to these issues...

See my .sig!

[Zarel]

As for if anyone is working on any of this, everyone is busy, so little is being done right now, but that don't mean we won't come back to these issues...

It's more that no one's really all that good at working around driver issues.

[stiv]

It's more that no one's really all that good at working around driver issues.

The two problems with 'working around' driver issue are
a) you need the specific OS, video card & driver to do any development
b) workarounds tend to break all the other working platforms.