- Joined
- Jun 18, 2011
- Messages
- 79
I have an interesting problem that some people are experiencing while loading my new custom map RPG Battle Siege. I myself do not have this issue at all... and many others do not as well. Although some people, especially LABTOP users are crashing the moment the game would begin for them.
I did some research online and have found possible problem causes... According to online, some custom models or doodads may cause some people to crash while they run custom maps, or even some initital triggers may as well.
I do not use any map INIT triggers, everything that would normally be MAP INIT is rather a 0.03 elapsed time. And even if I were to transfer my trigs into INIT trigs I would still only have 3 initial triggers, and they are all trigs I have used in my MTG map and this problem never occurred for that map.
Regarding doodads my map doesnt use any at this point at all. But I am using many custom models, and some date back to 2004. So I have reason to believe it might be one of the custom models that is causing this issue. If thats the case I have to slowly weed them down 1 by 1 and hopefully find the one that is causing the problem. But each model I use is from this website (HIVE) and you would figure their shouldnt be an issue right? Anyhow, any advice or method I can take on this subject to help speed this process up would be much appreciated.
I did some research online and have found possible problem causes... According to online, some custom models or doodads may cause some people to crash while they run custom maps, or even some initital triggers may as well.
I do not use any map INIT triggers, everything that would normally be MAP INIT is rather a 0.03 elapsed time. And even if I were to transfer my trigs into INIT trigs I would still only have 3 initial triggers, and they are all trigs I have used in my MTG map and this problem never occurred for that map.
Regarding doodads my map doesnt use any at this point at all. But I am using many custom models, and some date back to 2004. So I have reason to believe it might be one of the custom models that is causing this issue. If thats the case I have to slowly weed them down 1 by 1 and hopefully find the one that is causing the problem. But each model I use is from this website (HIVE) and you would figure their shouldnt be an issue right? Anyhow, any advice or method I can take on this subject to help speed this process up would be much appreciated.