Journals
For those who still map for HLDM, I found the following by messing around in the SP maps while on a LAN server.
1. Barnacles, (the apache, can't remember plural for it), turrets,sitting scientists, and dead monsters can be placed in a HLDM map.
2. Scripted sequences do not fire all the time. (I ran across the bridge that gets destroyed in surface tension :D)
3. It's fun to just run around the SP maps when you're insanely bored.
For those HLDM mappers who did'nt know about the monsters, I hope I gave you inspiration.
1. Barnacles, (the apache, can't remember plural for it), turrets,sitting scientists, and dead monsters can be placed in a HLDM map.
2. Scripted sequences do not fire all the time. (I ran across the bridge that gets destroyed in surface tension :D)
3. It's fun to just run around the SP maps when you're insanely bored.
For those HLDM mappers who did'nt know about the monsters, I hope I gave you inspiration.
I was bored the other day, so I wrote a short story. Enjoy.
The Rise and Fall of Floating Point
A badly-written short story, by Penguinboy
(Warning: this is a work of fiction. Like most fiction, it has a bit of fact within it, but none of the information here is accurate. This story doesn't represent the author's views.)
Chapter 1: Ancient History
When computers were first introduced, all numbers represented within a program were in binary form. The programmers did amazing things with the binary numbers, and the people rejoiced. One day, a bloke by the name of Bob thought, "But I don't count in binary, I count in decimal!". Bob asked the other programmers why they used binary instead of decimal, and the programmers laughed at Bob and called him names (like Snob, Gob, Drongo, etc). Bob wouldn't have any of that, so he shot the mean programmers.
The next day Bob used the power of Morse code to transform all programming languages to use decimal instead of binary formatting. He showed this to a programmer (as there were new ones to replace the others), and the programmer was so shocked to see a '2' in Bob's code, he fainted. Once he recovered, the programmer praised Bob for being such an evolutionary guy, and the people rejoiced. The world flourished under Bob's rule, and programming with regular decimal integers allowed everyone to write their own code.
Many years later, a sheila by the name of Jess was happily programming on her electric keyboard, when suddenly, she saw a problem with the current method of programming with whole integers. She gained an audience with King Bob, and told him her problem.
"I want to use a decimal point in my numbers", Jess told Bob.
Bob thought this was a ridiculous idea. "I think that is a ridiculous idea", he said to Jess, and had her beheaded.
But it was too late. A lone programmer, called Fred, heard Jess's idea, and thought it was not a ridiculous idea at all. He started a cult, which he called "The Jess Initiative" (TJI). He kept TJI a secret from Bob, and started implementing a programming language in secret, because it used illegal binary numbers. Fred had a very good idea of how to use decimal points in his code, which he called "Floating Point". Once he had finished his program, he rejoiced (quietly, and in secret).
Fred approached the King and challenged him to a programming battle, as was the custom. Bob scoffed at Fred, for he was very short, but he accepted the challenge anyway. Once the battle started, it was obvious that Bob had no chance of winning. Fred's program was much more accurate than Bob's, because it had the advantage of decimal precision, where Bob's did not. Bob was killed in the battle, and Fred was crowned the new king. He told the people about floating points, and they rejoiced.
Chapter 2: The Story of John and Gabe
Many years later, A programmer named John Carmack appeared out of nowhere. He astonished all the other programmers with his skill, and quickly became renowned as the best programmer in the land. He gained many followers, and together they named themselves "id". The id group did what nobody else has done before, and made a 3D engine. Early in the development process, the following conversation took place:
"We need a file format to represent a map." Said John to id programmer #1, who we shall call id1.
id1 replied, "Well, our engine only supports maps that are an intersection of planes, so we should represent maps like that."
"Good idea," John said. "Can you make it so that our level editor can edit the map directly, without us having to do any sort of compile process?"
"That'll take me at least a day to implement." Noted id1. "Let's just leave the compile process in there. Nobody will notice the difference."
John thought about it. "You're right. People enjoy compiling, anyway."
The event recorded above is known as "id's First Great Mistake". Many would come to regret the decision, including John himself. But, for now, he and the rest of id rejoiced. The file format was introduced, and was christened with the name "MAP", as id believed their format to be the only format for maps the world would ever need.
As the format was implemented, a few problems quickly arose. The floating point system was producing small, but very important, rounding errors. No program had ever needed to be that accurate before, so the problem had been previously undetected. Carmack knew the consequences of questioning the authority of the floating point system (or face the wrath of Fred), so he quickly eliminated the programmer that found the error, and he covered it up with some basic rounding functions.
id released their 3D engine in the form of a game, and it was called Quake. Quake impressed a lot of people, including one known as Gabe Newell. Gabe approached a programmer friend of his, Mike, and they eloped and formed their own studio, which they called Valve (the name derived from Quake developers' strange fear of the word "Leak", and you can tighten a valve to stop leaking pipes, or something like that). Valve employed the use of the Quake engine to make a game called Half-Life. Half-Life was a very good game, and the people rejoiced.
Gabe decided to make a sequel to Half-Life. He told his Valve friends so, and they all agreed that they should make their own 3D engine, to prove how awesome they were. During development, they discovered that the MAP format was not suitable for their needs:
"We need to make our own format." said Valve programmer #1 (vp1).
"Okay", said Gabe, "Can you make it use the same plane-intersection technique as MAP, though? That way our programmers would already be familiar with the system."
"That makes sense." Replied vp1. "I shall get on it immediately. I could set aside a day to get rid of the compiling process, too, if you want."
"Are you kidding?" asked Gabe. "Level designers love compiling!"
"Wow, what was I thinking? Of course, you're right." said vp1. "You're incredibly smart."
"I know." said Gabe. "Now let's go and frolic in the daffodil fields."
"Do let's." replied vp1.
And go they did.
So Valve continued to use the plane-intersection representation of world geometry in their new format (VMF), and some code from the quake engine was copied over to accommodate for that. Little did they know that the magic floating point rounding algorithm was contained within. Valve later released Half-Life 2 in their new engine called "Source". It was named so because they were unable to copyright "Sauce", because the name was too generic. The reason they wanted "Sauce" is unknown.
Years passed, and John decided to release the Quake source code to the world, for it was no longer of any use to him. The floating point problem was quickly found (which John had forgotten about), and John was sentenced to death by big-rock-dropped-on-head (later known as Crushing) by King Fred. But before he could be executed, a rebellion took place (for the people loved John), and King Fred was overthrown. John refused the people's offer to become the new leader, instead leaving to work on Doom 3 (aka "id's Second Great Mistake"). Fred was eventually replaced by a man called Obama, who relaxed restrictions on programming, so people could code without fear.
Chapter 3: The Fall
Many more years later, a young programmer was doing some research into the story told above. He saw the MAP and VMF formats, and their similarities and differences. He investigated the intersection of planes algorithm, and experienced the same floating point rounding issues that many others before him had encountered. By this time, a programming language had been invented with a "decimal" format.
The decimal format was not a native format, and was therefore slower than floating point. But, it had the advantage of being much more accurate than floating point, having no rounding errors. The young programmer noted this, and used the power of email to eliminate floating point from all the world's programming languages. But the power of email is not as influential as the power of Morse code, so the attempt failed. The young programmer had to make do with modifying his program to use decimals instead of floating points. The program worked much better, and the rounding errors disappeared. The young programmer rejoiced.
Remember the failure of the young programmer. Floating points are fast, easy to manipulate, and native to many CPU's. They cannot be destroyed. Even now, floating points are kidnapping children in their sleep, running over cats for the fun of it, and cutting in line at theme parks. They should be avoided at all costs! If you see a floating point on the street, run away as fast as you can.
You have been warned.
The Rise and Fall of Floating Point
A badly-written short story, by Penguinboy
(Warning: this is a work of fiction. Like most fiction, it has a bit of fact within it, but none of the information here is accurate. This story doesn't represent the author's views.)
Chapter 1: Ancient History
When computers were first introduced, all numbers represented within a program were in binary form. The programmers did amazing things with the binary numbers, and the people rejoiced. One day, a bloke by the name of Bob thought, "But I don't count in binary, I count in decimal!". Bob asked the other programmers why they used binary instead of decimal, and the programmers laughed at Bob and called him names (like Snob, Gob, Drongo, etc). Bob wouldn't have any of that, so he shot the mean programmers.
The next day Bob used the power of Morse code to transform all programming languages to use decimal instead of binary formatting. He showed this to a programmer (as there were new ones to replace the others), and the programmer was so shocked to see a '2' in Bob's code, he fainted. Once he recovered, the programmer praised Bob for being such an evolutionary guy, and the people rejoiced. The world flourished under Bob's rule, and programming with regular decimal integers allowed everyone to write their own code.
Many years later, a sheila by the name of Jess was happily programming on her electric keyboard, when suddenly, she saw a problem with the current method of programming with whole integers. She gained an audience with King Bob, and told him her problem.
"I want to use a decimal point in my numbers", Jess told Bob.
Bob thought this was a ridiculous idea. "I think that is a ridiculous idea", he said to Jess, and had her beheaded.
But it was too late. A lone programmer, called Fred, heard Jess's idea, and thought it was not a ridiculous idea at all. He started a cult, which he called "The Jess Initiative" (TJI). He kept TJI a secret from Bob, and started implementing a programming language in secret, because it used illegal binary numbers. Fred had a very good idea of how to use decimal points in his code, which he called "Floating Point". Once he had finished his program, he rejoiced (quietly, and in secret).
Fred approached the King and challenged him to a programming battle, as was the custom. Bob scoffed at Fred, for he was very short, but he accepted the challenge anyway. Once the battle started, it was obvious that Bob had no chance of winning. Fred's program was much more accurate than Bob's, because it had the advantage of decimal precision, where Bob's did not. Bob was killed in the battle, and Fred was crowned the new king. He told the people about floating points, and they rejoiced.
Chapter 2: The Story of John and Gabe
Many years later, A programmer named John Carmack appeared out of nowhere. He astonished all the other programmers with his skill, and quickly became renowned as the best programmer in the land. He gained many followers, and together they named themselves "id". The id group did what nobody else has done before, and made a 3D engine. Early in the development process, the following conversation took place:
"We need a file format to represent a map." Said John to id programmer #1, who we shall call id1.
id1 replied, "Well, our engine only supports maps that are an intersection of planes, so we should represent maps like that."
"Good idea," John said. "Can you make it so that our level editor can edit the map directly, without us having to do any sort of compile process?"
"That'll take me at least a day to implement." Noted id1. "Let's just leave the compile process in there. Nobody will notice the difference."
John thought about it. "You're right. People enjoy compiling, anyway."
The event recorded above is known as "id's First Great Mistake". Many would come to regret the decision, including John himself. But, for now, he and the rest of id rejoiced. The file format was introduced, and was christened with the name "MAP", as id believed their format to be the only format for maps the world would ever need.
As the format was implemented, a few problems quickly arose. The floating point system was producing small, but very important, rounding errors. No program had ever needed to be that accurate before, so the problem had been previously undetected. Carmack knew the consequences of questioning the authority of the floating point system (or face the wrath of Fred), so he quickly eliminated the programmer that found the error, and he covered it up with some basic rounding functions.
id released their 3D engine in the form of a game, and it was called Quake. Quake impressed a lot of people, including one known as Gabe Newell. Gabe approached a programmer friend of his, Mike, and they eloped and formed their own studio, which they called Valve (the name derived from Quake developers' strange fear of the word "Leak", and you can tighten a valve to stop leaking pipes, or something like that). Valve employed the use of the Quake engine to make a game called Half-Life. Half-Life was a very good game, and the people rejoiced.
Gabe decided to make a sequel to Half-Life. He told his Valve friends so, and they all agreed that they should make their own 3D engine, to prove how awesome they were. During development, they discovered that the MAP format was not suitable for their needs:
"We need to make our own format." said Valve programmer #1 (vp1).
"Okay", said Gabe, "Can you make it use the same plane-intersection technique as MAP, though? That way our programmers would already be familiar with the system."
"That makes sense." Replied vp1. "I shall get on it immediately. I could set aside a day to get rid of the compiling process, too, if you want."
"Are you kidding?" asked Gabe. "Level designers love compiling!"
"Wow, what was I thinking? Of course, you're right." said vp1. "You're incredibly smart."
"I know." said Gabe. "Now let's go and frolic in the daffodil fields."
"Do let's." replied vp1.
And go they did.
So Valve continued to use the plane-intersection representation of world geometry in their new format (VMF), and some code from the quake engine was copied over to accommodate for that. Little did they know that the magic floating point rounding algorithm was contained within. Valve later released Half-Life 2 in their new engine called "Source". It was named so because they were unable to copyright "Sauce", because the name was too generic. The reason they wanted "Sauce" is unknown.
Years passed, and John decided to release the Quake source code to the world, for it was no longer of any use to him. The floating point problem was quickly found (which John had forgotten about), and John was sentenced to death by big-rock-dropped-on-head (later known as Crushing) by King Fred. But before he could be executed, a rebellion took place (for the people loved John), and King Fred was overthrown. John refused the people's offer to become the new leader, instead leaving to work on Doom 3 (aka "id's Second Great Mistake"). Fred was eventually replaced by a man called Obama, who relaxed restrictions on programming, so people could code without fear.
Chapter 3: The Fall
Many more years later, a young programmer was doing some research into the story told above. He saw the MAP and VMF formats, and their similarities and differences. He investigated the intersection of planes algorithm, and experienced the same floating point rounding issues that many others before him had encountered. By this time, a programming language had been invented with a "decimal" format.
The decimal format was not a native format, and was therefore slower than floating point. But, it had the advantage of being much more accurate than floating point, having no rounding errors. The young programmer noted this, and used the power of email to eliminate floating point from all the world's programming languages. But the power of email is not as influential as the power of Morse code, so the attempt failed. The young programmer had to make do with modifying his program to use decimals instead of floating points. The program worked much better, and the rounding errors disappeared. The young programmer rejoiced.
Remember the failure of the young programmer. Floating points are fast, easy to manipulate, and native to many CPU's. They cannot be destroyed. Even now, floating points are kidnapping children in their sleep, running over cats for the fun of it, and cutting in line at theme parks. They should be avoided at all costs! If you see a floating point on the street, run away as fast as you can.
You have been warned.
Finished the Blitz Rifle 2.
Included:
View model
World model
Player model
Ammo model
Grenade fired model
Grenade world model
Sprites
Sounds
Download.
Screens:
Included:
View model
World model
Player model
Ammo model
Grenade fired model
Grenade world model
Sprites
Sounds
Download.
Screens:
For anyone who has Farcry 2, check out my new map, for the Moddb Farcry 2 competition!
http://www.moddb.com/games/far-cry-2/addons/liberty-2014
http://www.moddb.com/games/far-cry-2/addons/liberty-2014
'< ' '' '' ' '' ' '' ' ' ' '' '
While you're signing your petitions against and boycotting google, check out the newest release of Rooms!Rooms Mappack
Rooms Hammer Files
Poll:
What movie would you see if you were going tonight?
a. The Curious Case Of Benjamin Button
b. Yes Man
c. The Unborn
d. Valkyrie
i already saw 7 pounds, it wasn't bad.
What movie would you see if you were going tonight?
a. The Curious Case Of Benjamin Button
b. Yes Man
c. The Unborn
d. Valkyrie
i already saw 7 pounds, it wasn't bad.
Yay, Its my birthday today!
Bonus points if you can correctly guess my age.
Bonus points if you can correctly guess my age.
Learning to jump the skateboard.
I'm an idiot.
Playing FarCry 2 now:
From me being careless ended up destroying my 6800XT and now I've reverted back to the ever so old 5200FX. I attempted to unlock some pipelines only realising it destroyed parts of the actual hardware. The dialogue box clearly stated, 'use it at your own risk' and now I regret actually opening RivaTuner. I learnt my lesson now... Time look for another graphics card. Looking for AGP card below $100. And yes, the budget is tight.
Well, the funeral is in procession. I've obtained a coffin, the preservations, but no locks yet. I'm about to send my Xbox 360 off to the lovely Microsoft graveyard for revival or removal. Whatever comes first. I was receiving the wonderful 3-Ring light error which usually means a hardware malfunction, and the current symptoms indicate GPU problems, mostly likely melting from its soldering.
In any case, I've got everything I need but the tape. >_>
In any case, I've got everything I need but the tape. >_>
Well I'm back,
I spent the past 12 days in Colombia. Now I am back to spam here again.
I spent the past 12 days in Colombia. Now I am back to spam here again.
I got a Logitech G5 mouse as a late Christmas present, so here's a long ass review I wrote out of boredom. You'll be in a catatonic stupor by the time you're done reading it.
This mouse is actually the second generation of G5 laser mice on the market. It's apparently been somewhat upgraded from the first generation, which only had one thumb button and a different surface texture design. Other than that I'm not sure if anything's changed.
Same generic Logitech packaging as any other mouse they make.
There's actually a fair few more doohickies included here than any other mouse I've purchased. You've got your mouse, a case of weights, the weight cartridge, and a driver disc. At first I thought the 50 dollar price tag was a bit much compared to what my old Mx518 cost, but from the looks of things I think I was mistaken.
Inside the rather nicely designed padded case are a large collection of weights of either 1.7 or 4.5 grams a piece. I'm not really sure where Logitech came up with a number like 1.7 grams, but there you have it. These small cylindrical weights are to be arranged in a little clear blue cartridge with eight available slots. This offers an insane amount of customization, and honestly I think I'd be happier if there were something like three selectable weights instead of this little case and with sixteen miniscule weights to be lost amongst the clutter on my desk. I highly doubt even a "professional gamer" would notice the difference if they'd used a simplified system, but that's just me.
Once the weights are inside the little cartridge, you slide it into a little slot on the bottom of the mouse that holds it in place with a plastic tab. I'm actually not too thrilled with any part of this mechanism. I considered the last Logitech mouse I had, an Mx518, to be damn near indestructible. You wouldn't believe the amount of abuse that thing stood up to, and from its exterior condition it has no right to be operational. I believe its structural integrity stemmed from Logitech's use of very high quality plastics. While the mouse appears to be constructed the same way with the G5, the quality of this plastic slot is highly questionable. It lends a rattling noise to the mouse if you shake it around, and the weight cartridge will actually pop out by itself if you're too rough with it. That doesn't scream of unrivaled durability. In fact, I think Logitech only included this feature to give people a viable reason to upgrade.
The cord is a substantial upgrade from any other I've seen. It's coated with some kind of durable fabric material that lends a ropey feel to it. This also makes it extremely stiff and pliable, so once you've unwrapped the cord it won't snake itself back up into a tangle. If you're choosing to go wired, you should do it the right way.
The texture atop the G5 is a departure from the norm for me. Whereas my Mx518 was slick, this has a kind of papery scale-like feel to it. It's one of those neat coatings you have to feel to appreciate. The black sides of the mouse also have a grainy coating on them. That's good, because the rubber coating on my Mx518 wore out and started peeling. This new surface actually seems to absorb the sweat on your hands a bit, so instead of getting all slippery it simply improves the grip. The DPI buttons are positioned differently than on my old mouse, so that takes a bit of getting used to. I consider the old button setup more intuitive. The DPI indicator is cool too, though I'd never look at it while in use.
The scroll wheel now has a very annoying side-press button feature which makes pressing the center button quite a chore. Half the time you hit these side-press buttons it's an accident, so I consider them useless. Unfortunately, the addition of this feature required the hole around the scroll wheel to be widened for movement. The very thing that caused problems with my Mx518 was that dirt and dust got jammed in the scroll wheel and caused erratic scrolling behavior. A bigger hole will just promote this.
The G5 has these newfangled Polytetraoverlycomplicatedname feet on it, and it really does glide smooth as silk. I'm using a Black Knight XH mouse pad, and I hardly notice the difference between its surface and my fake woodgrain desktop. The tracking of the new "gaming grade" laser eye is probably a vast technical improvement over the old optical system, but in the real world I can't notice a bit of difference.
I didn't have to install any software for this mouse to work, just plugged it in and everything worked. That was a relief to me, because I absolutely hate software like the included SetPoint to be running in the background.
Overall, what you've got here is a really great Logitech mouse with a couple new features over older, less costly models. I couldn't recommend that anyone upgrade from a functional 518 or 510, but if you're currently working on a crappy old generic optical mouse, it's well worth it to spend the extra ten or fifteen bucks over older models... just as long as you can put up with some slight rattling.
This mouse is actually the second generation of G5 laser mice on the market. It's apparently been somewhat upgraded from the first generation, which only had one thumb button and a different surface texture design. Other than that I'm not sure if anything's changed.
The scroll wheel now has a very annoying side-press button feature which makes pressing the center button quite a chore. Half the time you hit these side-press buttons it's an accident, so I consider them useless. Unfortunately, the addition of this feature required the hole around the scroll wheel to be widened for movement. The very thing that caused problems with my Mx518 was that dirt and dust got jammed in the scroll wheel and caused erratic scrolling behavior. A bigger hole will just promote this.
The G5 has these newfangled Polytetraoverlycomplicatedname feet on it, and it really does glide smooth as silk. I'm using a Black Knight XH mouse pad, and I hardly notice the difference between its surface and my fake woodgrain desktop. The tracking of the new "gaming grade" laser eye is probably a vast technical improvement over the old optical system, but in the real world I can't notice a bit of difference.
I didn't have to install any software for this mouse to work, just plugged it in and everything worked. That was a relief to me, because I absolutely hate software like the included SetPoint to be running in the background.
Overall, what you've got here is a really great Logitech mouse with a couple new features over older, less costly models. I couldn't recommend that anyone upgrade from a functional 518 or 510, but if you're currently working on a crappy old generic optical mouse, it's well worth it to spend the extra ten or fifteen bucks over older models... just as long as you can put up with some slight rattling.