Re: PID for OS X


	/-/S'pht-Translator-Active/-/

Re: PID for OS X

Posted By: Ron Hunsinger Date: 4/15/13 7:53 p.m.
In Response To: PID for OS X (Godot)

The way I learned about the new version was in a Google+ message that included the comment:
"And +Ron Hunsinger just lost another 4 months of his life..."
Ha! 3 months, tops.
I downloaded it immediately, but feared it might be only a partial port. Right off the bat, I tried the ANYWHERE hack (which I unashamedly exploit wantonly), and was delighted that it worked! I figured if they got that right, they probably got it all right. I didn't even notice the new cheat message until someone mentioned it here.
I'm currently on I'd Rather be Surfing, with no damage (except from Blue Pods) and 100% accuracy (thanks to ANYWHERE). After I finish, I intend to go back and do it again without using ANYWHERE.
I did find a few places where the port is less than perfect.
In the original game, you can normally save only if you're on or in a cell adjacent to a Save Rune. The ANYWHERE hack changes the definition of "adjacent" to mean "on the same level". That is, you still can't save on Labyrinth or OKWEWS, because those levels don't have Save Runes.
But I was getting beat up on Labyrinth, and idly tried saving there. To my surprise, it let me! I expected that would make Labyrinth a cake-walk, but no. Restoring from such a saved position crashes the game.
In hindsight, I realize the problem. Normally, levels are written out to the Save Game file when you save or leave the level, but there's special code to skip writing Labyrinth or OKWEWS, because those levels are always custom-built from their pristine state when you arrive. Which means, if you restore to Labyrinth, there's a good chance you'll appear inside a wall. (Or inside a Shocking Sphere.)
I wonder what will happen if I save on OKWEWS? The walls there don't move, and what I remember of the arrive-on-level code should make it work as long as you save while standing where monsters won't be. They should re-populate at their normal positions.
If the source code this game is based on doesn't block saving on Labyrinth and OKWEWS, maybe it's an older version that still also has the bug that lets you kill the Dreaming God multiple times, to get multiple gemstones. I guess I'll find out when I get there.
I was hoping this version would at least fix the bug in the random number generator that causes Shocking Spheres to concentrate around the ladders from HHCC and Lasciate... . Nope. There's still almost always one of them on your left when you enter in those corners. (Hint: the fix is as simple as using a better random number generator, for example a linear congruential method using a modulus that is not a power of 2. Or, when generating random x,y coordinates for a sphere, instead of using random() % 32 for each coordinate, use random() % 30 + 1. )
I can only assume the bug is still there that corrupts the LevelState data when a monster tries to shoot and there isn't room to make a bullet. (It makes the bullet anyway, but on top of some unrelated data, which it clobbers.) That bug makes it difficult to boost your "+1 for each 250 kills" bonus.
Some of the keyboard shortcuts are missing. I'm accustomed to hitting back-quote (or ESC or keypad-clear) to switch quickly between the World View and Inventory windows. None of those work in this version.
I can't rearrange items inside a container. (For example, to pre-load one kind of ammo at the top of a canvas bag.) Dragging something to a container tends to open it, which is a nuisance. Worse, dragging within the Inventory window doesn't necessarily select it, so time is still running in the game when I think it's paused.
It looks like the Inventory window at least was re-written in Cocoa, and these are all birth pains of the new code. I'm confident they'll be fixed.
Overall, I'm delighted! Great work, guys!

[ Post a Reply | Message Index | Read Prev Msg | Read Next Msg ]
Pre-2004 Posts

Replies:

PID for OS X Godot 4/9/13 7:02 a.m.

Re: PID for OS X treellama 4/9/13 7:39 a.m.

Re: PID for OS X Mark Levin 4/9/13 8:28 a.m.

Re: PID for OS X Destiny 4/9/13 8:49 a.m.

Re: PID for OS X Hopper 4/9/13 10:03 a.m.

Re: PID for OS X Mark Levin 4/9/13 10:28 a.m.

Re: PID for OS X lucas93 4/9/13 3:08 p.m.

Re: PID for OS X Yossarian 4/9/13 3:59 p.m.

Re: PID for OS X selbstmord 4/11/13 7:40 a.m.

Re: PID for OS X President People 4/11/13 3:00 p.m.

Re: PID for OS X ukimalefu 4/11/13 11:38 p.m.

Re: PID for OS X PerseusSpartacus 4/12/13 12:04 a.m.

Re: PID for OS X PerseusSpartacus 4/9/13 8:25 p.m.

Re: PID for OS X ukimalefu 4/10/13 12:17 a.m.

Re: PID for OS X Godot 4/10/13 12:34 a.m.

Re: PID for OS X ukimalefu 4/10/13 12:36 a.m.

Re: PID for OS X Mark Levin 4/10/13 6:08 a.m.

Re: PID for OS X Godot 4/10/13 6:29 a.m.

Re: PID for OS X Godot 4/10/13 6:32 a.m.

Re: PID for OS X Hopper 4/10/13 7:31 a.m.

Re: PID for OS X Mark Levin 4/10/13 8:20 a.m.

Re: PID for OS X PerseusSpartacus 4/10/13 9:22 a.m.

Re: PID for OS X Hopper 4/10/13 11:07 a.m.

Re: PID for OS X PerseusSpartacus 4/10/13 11:21 a.m.

Re: PID for OS X MrM12LRV 4/10/13 2:29 p.m.

SPOILER ALERT! You need to find this ukimalefu 4/11/13 2:08 a.m.

Re: PID for OS X Ron Hunsinger 4/15/13 7:53 p.m.

Re: PID for OS X Mark Levin 4/16/13 6:54 a.m.

Re: PID for OS X Ron Hunsinger 4/16/13 5:21 p.m.

Re: PID for OS X Mark Levin 4/16/13 6:00 p.m.

Re: PID for OS X Ron Hunsinger 4/16/13 7:50 p.m.

Re: PID for OS X Mark Levin 4/16/13 8:46 p.m.

Re: PID for OS X Hopper 4/17/13 6:11 a.m.

Re: PID for OS X Mark Levin 4/17/13 7:16 a.m.

Re: PID for OS X Hopper 4/17/13 8:14 a.m.

Re: PID for OS X Ron Hunsinger 4/18/13 1:01 a.m.

Re: PID for OS X Ron Hunsinger 4/18/13 1:09 a.m.

Re: PID for OS X Hopper 4/19/13 7:32 a.m.

Re: PID for OS X Mark Levin 4/19/13 8:28 a.m.

Re: PID for OS X Ron Hunsinger 4/19/13 7:33 p.m.

Re: PID for OS X Ron Hunsinger 4/18/13 3:11 a.m.

Re: PID for OS X Hopper 4/17/13 7:01 a.m.

Re: PID for OS X Mark Levin 4/17/13 7:12 a.m.

Re: PID for OS X Hopper 4/17/13 7:50 a.m.

Re: PID for OS X PerseusSpartacus 4/18/13 8:14 p.m.

Re: PID for OS X ukimalefu 4/19/13 2:41 a.m.

Re: PID for OS X Ron Hunsinger 4/19/13 4:10 a.m.

Re: PID for OS X PerseusSpartacus 4/19/13 6:31 p.m.

Re: PID for OS X Ron Hunsinger 4/19/13 7:55 p.m.

Re: PID for OS X treellama 4/20/13 5:11 a.m.

Re: PID for OS X PerseusSpartacus 4/20/13 9:38 a.m.

Re: PID for OS X bakudd 4/22/13 6:39 a.m.

PID 1.2 released Mark Levin 5/6/13 8:49 p.m.

Re: PID 1.2 released Godot 5/6/13 10:47 p.m.

Re: PID 1.2 released Hopper 5/7/13 10:31 a.m.

Re: PID 1.2 released ukimalefu 5/7/13 1:45 a.m.

[ Post a Reply | Message Index | Read Prev Msg | Read Next Msg ]
Pre-2004 Posts

Your Name:
Your E-Mail Address:
Subject:
Message:
: The way I learned about the new version was in a Google+ message that : included the comment: "And +Ron Hunsinger just lost another 4 months : of his life..." : Ha! 3 months, tops. : I downloaded it immediately, but feared it might be only a partial port. : Right off the bat, I tried the ANYWHERE hack (which I unashamedly exploit : wantonly), and was delighted that it worked! I figured if they got that : right, they probably got it all right. I didn't even notice the new cheat : message until someone mentioned it here. : I'm currently on I'd Rather be Surfing, with no damage (except from Blue : Pods) and 100% accuracy (thanks to ANYWHERE). After I finish, I intend to : go back and do it again without using ANYWHERE. : I did find a few places where the port is less than perfect. : In the original game, you can normally save only if you're on or in a cell : adjacent to a Save Rune. The ANYWHERE hack changes the definition of : "adjacent" to mean "on the same level". That is, you : still can't save on Labyrinth or OKWEWS, because those levels don't have : Save Runes. : But I was getting beat up on Labyrinth, and idly tried saving there. To my : surprise, it let me! I expected that would make Labyrinth a cake-walk, but : no. Restoring from such a saved position crashes the game. : In hindsight, I realize the problem. Normally, levels are written out to the : Save Game file when you save or leave the level, but there's special code : to skip writing Labyrinth or OKWEWS, because those levels are always : custom-built from their pristine state when you arrive. Which means, if : you restore to Labyrinth, there's a good chance you'll appear inside a : wall. (Or inside a Shocking Sphere.) : I wonder what will happen if I save on OKWEWS? The walls there don't move, : and what I remember of the arrive-on-level code should make it work as : long as you save while standing where monsters won't be. They should : re-populate at their normal positions. : If the source code this game is based on doesn't block saving on Labyrinth : and OKWEWS, maybe it's an older version that still also has the bug that : lets you kill the Dreaming God multiple times, to get multiple gemstones. : I guess I'll find out when I get there. : I was hoping this version would at least fix the bug in the random number : generator that causes Shocking Spheres to concentrate around the ladders : from HHCC and Lasciate... . Nope. There's still almost always one of them : on your left when you enter in those corners. (Hint: the fix is as simple : as using a better random number generator, for example a linear : congruential method using a modulus that is not a power of 2. Or, when : generating random x,y coordinates for a sphere, instead of using random() : % 32 for each coordinate, use random() % 30 + 1. ) : I can only assume the bug is still there that corrupts the LevelState data : when a monster tries to shoot and there isn't room to make a bullet. (It : makes the bullet anyway, but on top of some unrelated data, which it : clobbers.) That bug makes it difficult to boost your "+1 for each 250 : kills" bonus. : Some of the keyboard shortcuts are missing. I'm accustomed to hitting : back-quote (or ESC or keypad-clear) to switch quickly between the World : View and Inventory windows. None of those work in this version. : I can't rearrange items inside a container. (For example, to pre-load one : kind of ammo at the top of a canvas bag.) Dragging something to a : container tends to open it, which is a nuisance. Worse, dragging within : the Inventory window doesn't necessarily select it, so time is still : running in the game when I think it's paused. : It looks like the Inventory window at least was re-written in Cocoa, and : these are all birth pains of the new code. I'm confident they'll be fixed. : Overall, I'm delighted! Great work, guys!

If you'd like to include a link to another page with your message,
please provide both the URL address and the title of the page:
Optional Link URL:
Optional Link Title:

If necessary, enter your password below:
Password:

Problems? Suggestions? Comments? Email maintainer@bungie.org
Marathon's Story Forum is maintained with WebBBS 5.12.

PID for OS X	Godot	4/9/13 7:02 a.m.
Re: PID for OS X	treellama	4/9/13 7:39 a.m.
Re: PID for OS X	Mark Levin	4/9/13 8:28 a.m.
Re: PID for OS X	Destiny	4/9/13 8:49 a.m.
Re: PID for OS X	Hopper	4/9/13 10:03 a.m.
Re: PID for OS X	Mark Levin	4/9/13 10:28 a.m.
Re: PID for OS X	lucas93	4/9/13 3:08 p.m.
Re: PID for OS X	Yossarian	4/9/13 3:59 p.m.
Re: PID for OS X	selbstmord	4/11/13 7:40 a.m.
Re: PID for OS X	President People	4/11/13 3:00 p.m.
Re: PID for OS X	ukimalefu	4/11/13 11:38 p.m.
Re: PID for OS X	PerseusSpartacus	4/12/13 12:04 a.m.
Re: PID for OS X	PerseusSpartacus	4/9/13 8:25 p.m.
Re: PID for OS X	ukimalefu	4/10/13 12:17 a.m.
Re: PID for OS X	Godot	4/10/13 12:34 a.m.
Re: PID for OS X	ukimalefu	4/10/13 12:36 a.m.
Re: PID for OS X	Mark Levin	4/10/13 6:08 a.m.
Re: PID for OS X	Godot	4/10/13 6:29 a.m.
Re: PID for OS X	Godot	4/10/13 6:32 a.m.
Re: PID for OS X	Hopper	4/10/13 7:31 a.m.
Re: PID for OS X	Mark Levin	4/10/13 8:20 a.m.
Re: PID for OS X	PerseusSpartacus	4/10/13 9:22 a.m.
Re: PID for OS X	Hopper	4/10/13 11:07 a.m.
Re: PID for OS X	PerseusSpartacus	4/10/13 11:21 a.m.
Re: PID for OS X	MrM12LRV	4/10/13 2:29 p.m.
SPOILER ALERT! You need to find this	ukimalefu	4/11/13 2:08 a.m.
Re: PID for OS X	Ron Hunsinger	4/15/13 7:53 p.m.
Re: PID for OS X	Mark Levin	4/16/13 6:54 a.m.
Re: PID for OS X	Ron Hunsinger	4/16/13 5:21 p.m.
Re: PID for OS X	Mark Levin	4/16/13 6:00 p.m.
Re: PID for OS X	Ron Hunsinger	4/16/13 7:50 p.m.
Re: PID for OS X	Mark Levin	4/16/13 8:46 p.m.
Re: PID for OS X	Hopper	4/17/13 6:11 a.m.
Re: PID for OS X	Mark Levin	4/17/13 7:16 a.m.
Re: PID for OS X	Hopper	4/17/13 8:14 a.m.
Re: PID for OS X	Ron Hunsinger	4/18/13 1:01 a.m.
Re: PID for OS X	Ron Hunsinger	4/18/13 1:09 a.m.
Re: PID for OS X	Hopper	4/19/13 7:32 a.m.
Re: PID for OS X	Mark Levin	4/19/13 8:28 a.m.
Re: PID for OS X	Ron Hunsinger	4/19/13 7:33 p.m.
Re: PID for OS X	Ron Hunsinger	4/18/13 3:11 a.m.
Re: PID for OS X	Hopper	4/17/13 7:01 a.m.
Re: PID for OS X	Mark Levin	4/17/13 7:12 a.m.
Re: PID for OS X	Hopper	4/17/13 7:50 a.m.
Re: PID for OS X	PerseusSpartacus	4/18/13 8:14 p.m.
Re: PID for OS X	ukimalefu	4/19/13 2:41 a.m.
Re: PID for OS X	Ron Hunsinger	4/19/13 4:10 a.m.
Re: PID for OS X	PerseusSpartacus	4/19/13 6:31 p.m.
Re: PID for OS X	Ron Hunsinger	4/19/13 7:55 p.m.
Re: PID for OS X	treellama	4/20/13 5:11 a.m.
Re: PID for OS X	PerseusSpartacus	4/20/13 9:38 a.m.
Re: PID for OS X	bakudd	4/22/13 6:39 a.m.
PID 1.2 released	Mark Levin	5/6/13 8:49 p.m.
Re: PID 1.2 released	Godot	5/6/13 10:47 p.m.
Re: PID 1.2 released	Hopper	5/7/13 10:31 a.m.
Re: PID 1.2 released	ukimalefu	5/7/13 1:45 a.m.



	Your Name:
	Your E-Mail Address:
	Subject:
	Message: : The way I learned about the new version was in a Google+ message that : included the comment: "And +Ron Hunsinger just lost another 4 months : of his life..." : Ha! 3 months, tops. : I downloaded it immediately, but feared it might be only a partial port. : Right off the bat, I tried the ANYWHERE hack (which I unashamedly exploit : wantonly), and was delighted that it worked! I figured if they got that : right, they probably got it all right. I didn't even notice the new cheat : message until someone mentioned it here. : I'm currently on I'd Rather be Surfing, with no damage (except from Blue : Pods) and 100% accuracy (thanks to ANYWHERE). After I finish, I intend to : go back and do it again without using ANYWHERE. : I did find a few places where the port is less than perfect. : In the original game, you can normally save only if you're on or in a cell : adjacent to a Save Rune. The ANYWHERE hack changes the definition of : "adjacent" to mean "on the same level". That is, you : still can't save on Labyrinth or OKWEWS, because those levels don't have : Save Runes. : But I was getting beat up on Labyrinth, and idly tried saving there. To my : surprise, it let me! I expected that would make Labyrinth a cake-walk, but : no. Restoring from such a saved position crashes the game. : In hindsight, I realize the problem. Normally, levels are written out to the : Save Game file when you save or leave the level, but there's special code : to skip writing Labyrinth or OKWEWS, because those levels are always : custom-built from their pristine state when you arrive. Which means, if : you restore to Labyrinth, there's a good chance you'll appear inside a : wall. (Or inside a Shocking Sphere.) : I wonder what will happen if I save on OKWEWS? The walls there don't move, : and what I remember of the arrive-on-level code should make it work as : long as you save while standing where monsters won't be. They should : re-populate at their normal positions. : If the source code this game is based on doesn't block saving on Labyrinth : and OKWEWS, maybe it's an older version that still also has the bug that : lets you kill the Dreaming God multiple times, to get multiple gemstones. : I guess I'll find out when I get there. : I was hoping this version would at least fix the bug in the random number : generator that causes Shocking Spheres to concentrate around the ladders : from HHCC and Lasciate... . Nope. There's still almost always one of them : on your left when you enter in those corners. (Hint: the fix is as simple : as using a better random number generator, for example a linear : congruential method using a modulus that is not a power of 2. Or, when : generating random x,y coordinates for a sphere, instead of using random() : % 32 for each coordinate, use random() % 30 + 1. ) : I can only assume the bug is still there that corrupts the LevelState data : when a monster tries to shoot and there isn't room to make a bullet. (It : makes the bullet anyway, but on top of some unrelated data, which it : clobbers.) That bug makes it difficult to boost your "+1 for each 250 : kills" bonus. : Some of the keyboard shortcuts are missing. I'm accustomed to hitting : back-quote (or ESC or keypad-clear) to switch quickly between the World : View and Inventory windows. None of those work in this version. : I can't rearrange items inside a container. (For example, to pre-load one : kind of ammo at the top of a canvas bag.) Dragging something to a : container tends to open it, which is a nuisance. Worse, dragging within : the Inventory window doesn't necessarily select it, so time is still : running in the game when I think it's paused. : It looks like the Inventory window at least was re-written in Cocoa, and : these are all birth pains of the new code. I'm confident they'll be fixed. : Overall, I'm delighted! Great work, guys!
	If you'd like to include a link to another page with your message, please provide both the URL address and the title of the page:
	Optional Link URL:
	Optional Link Title:
	If necessary, enter your password below:
	Password: