Hello,
I'm trying to load some wmp levels inserting a car (I want to run the levels using a car :-) ).
Well, even if the car works (and the scripts also), when I try to load the level (run the game) I obtain the following error:

Script crash in physX_level_load: SYS

What does it mean? What can I check to solve this problem?

Thank you for your help!

I don't have the answer but I do have the exact same problem, and the same clue you have. The map crashes during the level_load. I tested the physics sample and it works fine. My game also works fine if I use the physics sample map and not my own. So there is something wrong in our custom maps. I rebuilt my map from scratch using the A8 WED but so far it has not fixed the problem. I will let you know if I find an answer.

If You could give your code then it would be a little easier
As I remember: I had this error when something was little wrong with my code & level had blocks.

The physics engine can be fussy. I'm not sure if this applies to PhysX but make sure you level has a sky cube in WED.

can you show the script you are using to initialise the PhysX and level?
It would give us more insight on what might be wrong

regards,

Well I think I have ruled out the script because trying to load my level in the physX sample script also makes that working script crash. My level also was working in A7 with ODE physics. It's just the upgrading to PhysX that seems to be showing a problem with it.

Which is why I tried rebuilding the level from scratch in A8 to see if that would fix the issue. So far no answer yet.

Hello,

I don't think the script is the problem. I used a level called "CITY" environment: CITY

I think there is a problem in the level. Please note I have commercial version, so I cannot build BSP levels (maybe it helps).

Thank you

Another clue. I was able to get another map working. The only difference I could see between the maps was the working map has 14,011 faces and the broken map has 28,840 faces.

An email to support has confirmed this to be a bug that will be fixed next version.

Thank you! This is a good news!