I've experienced this behaviour (bug?), too.
Workaround: Have a look at the ackphysx code, copy the physX_open and physX_level_load into your code, change the latter function as follows:
When ent_type == 4, you have a terrain. Now save its xyz-position somewhere (skills?) and register it afterwards.

Better solution: File a bug report.