Note... A7.6 Beta "...could be an engine bug":
In e-mail correspondence with JCL, we have found a Bug where a particular, very complicated model, will not allow the engine to run. The engine issues a warning:
"Error E1198 MyModel.MDL : Bad file format"
JCL looked into this and I quote his response:
"There seems to be indeed something wrong - could be an engine bug. We'll look into the matter and will fix it for the next update."
Also... even though I have yet to address this with JCL, When I set the polycollision variable to 0 (See note at bottom)
i.e. var enable_polycollision = 0;
The effect is different on either of my two computers.
1.) The flight model will not read the terrain and will not move either up or down...
2.) The flight model will move up and down but the seed of trees will not find the terrain and it will then not work.
-On the up-side the frame rate is very high.
-On the down-side the physics and collision is extremly poor and does not work as before A7.5.
-Therefore I have no choice other than to set this variable anything but 0 and this really hurts the frame rate.
I see many new and awesome fetures but still feel that A7.07 is the fastest and most stable version ever made available...
Later,
Paul
BTW...
If you get a chance, take a look at:
www.terrasame.comThe free downloads will be available soon...
Note:
Below comes from the manual:
enable_polycollision
Determines the behavior of the c_... collision instructions.
Range set at 0,
Ellipsoid collision system and physics engine disabled. The collision functions default to USE_AABB. This has the advantage of faster level loading and faster collision detection, however the collision hulls are Axis Aligned Bounding Boxes (AABB) rather than rotated ellipsoids. Only BSP levels are supported by the AABB collision system.
This is the range that I have used for years with perfect results.
.
