Printable View
When I use BlueStreak to export a map from 3DS Max 9, I receive an error message which states that I have no actors to export, and therefore, the module fails the export. I know that this is a problem with my map, because the tutorial map exports without problems, but I am unable to identify the issue, despite using both tutorials found online and the Gearbox official map-editing tutorial. Please advise.
Check a few things in your .max file before exporting.
1. Do you have a "frame" object? If not, make any primitive and name it "frame" (without quotes.)
2. Is your level linked to your frame object? If not, link it to the "frame" object. Go into heirarchy view (select by name, and check off "display subtree.)
3. Is your Frame object linked to something else? If it is, unlink it; level BSP source files cannot have the Frame linked to anything.
I must say, it's wonderful having a new member who pays attention to grammar conventions - we need more of you here.
most definitely a frame linking or naming error.
LOL XDQuote:
Originally Posted by FriedMetroid
I'm grateful for your help with my previous issue. It turns out that the problem was that the reference frame needed to be named "frame", and I named it "Reference Frame". Anyway, I now have another problem. When I try to use tool with the .jms file produced by the export, it says in the debug: Couldn't read map file './toolbeta.map'. Could this have something to do with the possible error message during exporting, which reads: --Unknown property: "name" in undefined. What does this mean and what do I need to do to rectify the problem? In response to the pronunciation question, it's pronounced read-d+per
The toolbeta error is nothing, ignore it.
I apologize for basically asking for a step-by-step walkthrough from the view of troubleshooting, but I'll appreciate help with the odd "--Unknown property: "name" in undefined" unknown error message when exporting. You were right when you said the toolbeta error was nothing however. Thank you in advance.
I would also like to ask another question, as it came up while testing Sapien to see if I would have future problems. When I load the tutorial scenario, Sapien starts to load it for a while, but suddenly quits and provides no reason for the action. Please advise.
Take a look at the bottom part of your debug.txt that's in you halo ce folder. If you can't figure out what's going on, post it here, someone should know what's going on. :)
Also, if you're wanting to get rid of the toolbeta.map error, create a new text file in your halo ce folder and name it toolbeta.map; It should shut tool up.
I am not able to upload a picture, so I'll copy and paste here:
07.14.07 16:08:02 sapien pc 01.00.00.0609 ----------------------------------------------
07.14.07 16:08:02 reference function: _write_to_error_file
07.14.07 16:08:02 reference address: 401b13
07.14.07 16:08:02 Couldn't read map file './sapienbeta.map'
07.14.07 16:08:03 CreateDevice succeeded with refresh rate = 0
07.14.07 16:08:07 Increasing sound decompression buffer size to 1048576 bytes
07.14.07 16:08:27 the gbxmodel tag 'weapons\sniper rifle\fp\fp' (tags\weapons\sniper rifle\fp\fp.gbxmodel) had an invalid header
07.14.07 16:08:28 failed to load weapon tag 'weapons\sniper rifle\sniper rifle'
07.14.07 16:08:28 failed to load item_collection tag 'item collections\single weapons\sniper rifle'
07.14.07 16:08:28 the gbxmodel tag 'weapons\sniper rifle\fp\fp' (tags\weapons\sniper rifle\fp\fp.gbxmodel) had an invalid header
07.14.07 16:08:28 failed to load weapon tag 'weapons\sniper rifle\sniper rifle'
07.14.07 16:08:28 failed to load item_collection tag 'item collections\single weapons\sniper rifle'
07.14.07 16:08:30 failed to load scenario tag 'levels\test\tutorial\tutorial'
07.14.07 16:08:30 need to get the following tags:
07.14.07 16:08:30 weapons\sniper rifle\fp\fp.gbxmodel
07.14.07 16:08:30 weapons\sniper rifle\fp\fp.gbxmodel
07.14.07 16:08:30
07.14.07 16:08:30 game_load() failed.
07.14.07 16:08:44 sapien pc 01.00.00.0609 ----------------------------------------------
07.14.07 16:08:44 reference function: _write_to_error_file
07.14.07 16:08:44 reference address: 401b13
07.14.07 16:08:44 Couldn't read map file './sapienbeta.map'
07.14.07 16:08:44 CreateDevice succeeded with refresh rate = 0
07.14.07 16:08:48 Increasing sound decompression buffer size to 1048576 bytes
07.14.07 16:08:53 the gbxmodel tag 'weapons\sniper rifle\fp\fp' (tags\weapons\sniper rifle\fp\fp.gbxmodel) had an invalid header
07.14.07 16:08:53 failed to load weapon tag 'weapons\sniper rifle\sniper rifle'
07.14.07 16:09:07 failed to load globals tag 'globals\globals'
07.14.07 16:09:07 couldn't load game globals (get new tags)
07.14.07 16:09:07 need to get the following tags:
07.14.07 16:09:07 weapons\sniper rifle\fp\fp.gbxmodel
07.14.07 16:09:07
07.14.07 16:09:07 game_load() failed.
The exporting error is here:
"--Unknown property: "name" in undefined"
This is what is highlighted in the script source code:
format "%\n%\n" geom_materials[m].name "<none>" to:jms
err, how so? Does the screenshot show what's missing in the scenario?
Your Sapien problem is caused by a corrupted sniper rifle first person model - though how exactly to go about fixing that without lots of explanation could be hard. I have no idea how it could have become corrupted unless something went wrong with your install or you did something to it, but you'll have to find a way to replace it eventually.
For your exporting error, check all of your materials - you must have one multi/sub-object, with all others as sub-materials. Check your level's geometry to be sure that there are no invalid material IDs, and that the correct material is applied to all geometry parts.
Appreciating all help so far. Would my best choice of action be to reinstall, or can you recommend a place to download uncorrupted versions of the sniper rifle model? This may be a stupid question, but if there is only one multi/sub-object, with all others as sub-materials, how do I apply different materials to different geometry parts?
Thank you all for the advice given above. My problems have been solved, and I have made a couple of simple small maps. Goodbye.