search

thoth23 / fpscreatorengine

Automatically exported from code.google.com/p/fpscreatorengine
1 stars 0 forks source link

Model Pack 53 causes crash on custom maps. #24

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Load a custom map 
2. Put any character from EAI's model pack 53 in.
3. Run game. Game compiles and works perfect until the blue screen comes to let 
you inside the game. Then it crashes.

What is the expected output? What do you see instead?
The error after the blue screen. After you click ok it says you are building a 
large map ect. Yet the map takes up 1.2GB. I even tried turning the memory cap 
off. For some reason it works when you use stock media maps. I tried multiple 
custom maps with different media and they all failed.

What version of the product are you using? On what operating system?
Windows 7 64 bit - 1.18B7

Please provide any additional information below.
Not sure if you can reproduce but any map I load and put his characters into I 
get this error. I attached a screen shot of it.

Original issue reported on code.google.com by mstrncm...@gmail.com on 1 Feb 2011 at 12:29

Attachments:

GoogleCodeExporter commented 9 years ago 
I only get this error on some characters on some maps

Original comment by Frans.Sk...@gmail.com on 1 Feb 2011 at 9:27

GoogleCodeExporter commented 9 years ago 
Hmm interesting I am getting it with any character I bloody add.

Original comment by mstrncm...@gmail.com on 1 Feb 2011 at 11:12

GoogleCodeExporter commented 9 years ago 
Trim down the custom map to the minimal amount of custom assets, then provide 
the FPM level and the assets so I can reproduce the issue. I am presuming you 
have run the cleaner to ensure old BIN files are not causing this one. This 
error is normally caused when an entity/segment part cannot be loaded due to a 
corrupt mesh file, or the level has lost track of a mesh or object file. Keep 
deleting chunks of the custom map until it starts working again, all the way 
back to an almost empty level. If the empty level still exhibits this issue, 
upload the FPM of that empty level. My guess is at some point it will start 
working before the level is completely empty, and then you (and I) know which 
'chunk' of media is at fault.

Original comment by LeeBamberTGC@gmail.com on 2 Feb 2011 at 1:23

GoogleCodeExporter commented 9 years ago 
I just discoverd that when i placed a character on cosmic prophets cave ground 
segment it works but if i move it to one of his NukeCity buildings i get the 
error

Original comment by Frans.Sk...@gmail.com on 2 Feb 2011 at 3:43

GoogleCodeExporter commented 9 years ago 
This also seems to happen whenever they are running as DAI and placed on an 
entity in the editor.  Got the same error when I placed DAI charactter on the 
round scifi table.

Original comment by cotton.j...@gmail.com on 2 Feb 2011 at 5:22

GoogleCodeExporter commented 9 years ago 
Updated this post to include a simple .FPM file containing ALL stock media and 
2 characters from Model pack 53. Same problem. Should be able to reproduce. 
Just run it when you load it.

Original comment by mstrncm...@gmail.com on 2 Feb 2011 at 6:15

Attachments:

GoogleCodeExporter commented 9 years ago 
Lee, I'm uploading a tweaked version of that same map in which it does not 
crash.  I'm thinking its spawn proximity to an entity. Should help isolate 
things a bit more.

Original comment by cotton.j...@gmail.com on 2 Feb 2011 at 6:52

Attachments:

GoogleCodeExporter commented 9 years ago 
commenting out the script line in main and shoot ai scripts (near the bottom) 
which read..

;//Open Doors
:nearactivatable=0:settarget,activatetarget=2

Keeps the crash from happening.  So maybe perhaps related to the doors getting 
spammed or something because as the level loads I hear a door open.

This script line was supposed to allow DAI to open doors and I was under the 
impression it was also in the stock script but after checking I see it isn't 
there.

Sean might know more about what's happening there because he had sent me that 
line to add and I remember seeing it work in 1.17 betas.

Original comment by cotton.j...@gmail.com on 2 Feb 2011 at 7:33

GoogleCodeExporter commented 9 years ago 
Hi Lee, 
 Hope you don't mind I took the liberty to fix this myself. Uploading now

Original comment by hockeykid230@gmail.com on 3 Feb 2011 at 3:39

GoogleCodeExporter commented 9 years ago 
If the original poster can confirm this as fixed for V118 BETA8, we can close 
this.

Original comment by LeeBamberTGC@gmail.com on 5 Feb 2011 at 3:54