Page 1 of 1

Posted: Feb 4th '08, 00:17
by Nobody
Here's the situation: I'm running Forge 1.0.4 on Basilisk II. I'm following the Forge section of the Marathon Infinity manual. I complete the first tutorial, which is just a two-poly room with a Player object and textures. I try to save, and everything looks fine. Later I tried to open the map, but all that opens opens a totally blank map. I've tried making several different sized maps with various features, but when I go to open them, they all open blank. What gives?

Also, thanks for giving me a minute of your time, and any help will be greatly appreciated.

Posted: Feb 4th '08, 01:35
by $lave
Maybe forge is corrupt... this sounds like more of a problem with your emulator though, maybe it should go in editors, emulation etc.?

Sorry, can't help you.. you're sure you're going to file>save, and after you made the map? [spnkr]

Posted: Feb 4th '08, 03:14
by Nobody
$lave wrote:Maybe forge is corrupt... this sounds like more of a problem with your emulator though, maybe it should go in editors, emulation etc.?
Hmm... tried reinstalling Forge to no avail. I doubt it's being caused by the emolator, though, since it can do everything else fine. Just FYI, its emulating Mac OS 7.5.5.
Sorry, can't help you.. you're sure you're going to file>save, and after you made the map? [spnkr]
Yeah [MErr] Thanks for the advice, though.

Posted: Feb 4th '08, 03:35
by Wrkncacnter
I don't know if this will help with the problem you're having, but Forge 1.0.4 doesn't work well with Basilisk II. You should try Forge 1.0.1

Posted: Feb 4th '08, 06:26
by Zott
but all that opens opens a totally blank map.
Could you describe this a little bit.

Is this like smearing textures and items/monsters present.

Or untextured walls and items are missing?

Posted: Feb 4th '08, 07:04
by CryoS
its like opening a new map thus you opened a saved map

Posted: Feb 6th '08, 02:11
by Nobody
Thanks for the advice, but Forge 1.0.1 has the same problem.
Could you describe this a little bit.
Like when you start Forge and choose New Level.

Maybe I'm doing something wrong, so let me clarify; I build a 2-poly room, fill the polys, create a player object, enter visual mode, texture the walls, and save. I exit Forge, run it again, open the map, and it's blank. I've tried creating more complex and simplistic maps, but it always comes up blank.

EDIT: I can open files E00.Ne Cede Malis, E02. Poor Yorick, E06. Acme Station, and N33. Duality from a file called "Demo Merge". Where'd this come from. . .? So maybe Basilisk can't write info but can only read it for some reason. . .I'm gonna go test out this idea. . . Nope, can write text docs & such. I'm stumped. [MFrown]

Posted: Feb 6th '08, 02:27
by The Thug
Nobody wrote:Thanks for the advice, but Forge 1.0.1 has the same problem.
I exit Forge, run it again, open the map, and it's blank.
Is draw mode blank, or is visual mode blank?
Nobody wrote:from a file called "Demo Merge". Where'd this come from. . .?
That folder is inside the forge folder with the Forge application.

Posted: Feb 6th '08, 02:31
by Nobody
Draw mode' blank. But I can't go into visual without a player object, can I?

Posted: Feb 6th '08, 02:36
by The Thug
Correct. Are you mapping in the initial mapping window or scrolling to the outer parts of the mapping area? If you don't map in the center portion of the map, when you open it up again, it won't show your map in the initial window. You'll have to scroll to where it was the last time. Does that make sense?

Posted: Feb 6th '08, 02:38
by Nobody
Yeah, it makes sense. I'm mapping dead center of the inial mapping window.

Posted: Apr 9th '08, 14:19
by jbosmans
Remembering from the old days, Forge v1.0.2 (or was it 1.0.1) was the last stable version usable on 68k CPU's (so not PowerPC).
I don't know if you're emulating a PowerPC (but I think not with BasiliskII).
The latter version had at least a very annoying bug with heights (they show up as floating point numbers around 1.x or 2.x instead of the proper ticks aka 1024, 2048 etc)

Another thing you might want if you're developing maps on a 68k mac is Ignore Zero Divides, this keeps your Mac (or BasiliskII) from crashing when there's a divide by zero instruction, as they're well known to happen when you're making maps with Pfhorte 2.0a14 and even Forge iirc. Might also be a good idea to increase the default assigned memory to the editors (select the app and choose Get Info).

My 2ç