1.5?
Posted: Thu Nov 18, 2004 11:02 pm
Have we conclusively determined if it's ever going to get released? (Suncho, if you're willing to release a hacked version of 1.4, why havn't you released the 1.5 beta?)
If you knew what I know, you would not say that.Thenior wrote:Why is the 1.5 patch wanted anyway? Seems 1.4 works fine...
STRESSTEST wrote:I have a Dog named "Egg Nog", Duper.Duper wrote:I wanna talk about EGG NOG !!!!!
We havesnoopy wrote:My point is: why hasn't someone in the community just released the 1.5 beta instead of waiting for outrage to do something?
Read the quote that Stress was referring to. He's answering a different question.CDN_Merlin wrote:And he said what?
hax!Krom wrote:If you knew what I know, you would not say that.Thenior wrote:Why is the 1.5 patch wanted anyway? Seems 1.4 works fine...
1.5 doesn't have cross platform compatibility. You can find the beta if you go looking, but it's not done.snoopy wrote:Have we conclusively determined if it's ever going to get released? (Suncho, if you're willing to release a hacked version of 1.4, why havn't you released the 1.5 beta?)
x2STRESSTEST wrote:2 of the mac players have PCs Javed and Fusion. Who else is there on mac that plays?
Linux guys are x86 based and are not stupid by any means since they have tackled Linux. So they can easily throw a WinOS on a partition with ease.
Personally, I say, lets go to the 1.5 patch
x3KompresZor wrote:x2STRESSTEST wrote:2 of the mac players have PCs Javed and Fusion. Who else is there on mac that plays?
Linux guys are x86 based and are not stupid by any means since they have tackled Linux. So they can easily throw a WinOS on a partition with ease.
Personally, I say, lets go to the 1.5 patch
ahh, what the hellPugwash wrote:x3KompresZor wrote:x2STRESSTEST wrote:2 of the mac players have PCs Javed and Fusion. Who else is there on mac that plays?
Linux guys are x86 based and are not stupid by any means since they have tackled Linux. So they can easily throw a WinOS on a partition with ease.
Personally, I say, lets go to the 1.5 patch
I been saying this for yearsUnix wrote:ahh, what the hellPugwash wrote:x3KompresZor wrote:x2STRESSTEST wrote:2 of the mac players have PCs Javed and Fusion. Who else is there on mac that plays?
Linux guys are x86 based and are not stupid by any means since they have tackled Linux. So they can easily throw a WinOS on a partition with ease.
Personally, I say, lets go to the 1.5 patch
x4
We got Javed to buy a PC.STRESSTEST wrote:2 of the mac players have PCs Javed and Fusion. Who else is there on mac that plays?
Uh... no.Duper wrote:Most new mac's are going to be Linux based anyways.
There are many bug fixes as well, ohh.. like Suncho's pet peeve, the Omega. Maybe Suncho will be gracious enough to post the change log that is 1.5. Alex?punisher wrote: What, exactly, is the 1.5 patch going to do for me?
Likewise. I haven't been able to actually play it since it was released two or so years ago.DCrazy wrote:I think we're past the point where releasing the patch matters or not. There isn't even any more autoupdate for newbies (which we don't have) to get the patch. And I want more than 4 people to have played OG3.
Descent 3 v1.5 Readme 10/22/2001 wrote:Fixes for Version 1.5.0:
- Fixed a checksum problem introduced in 1.4 that prevented some levels from being played across platforms (for example, Windows and Linux).
- Force feedback now works under Windows 2000.
- Fixed crash starting a multiplayer game when the Black Pyro is the only allowed ship and the player is currently set to use another ship.
- Can no longer start a multiplayer game with no allowed ships.
- It's no longer possible to crash the dedicated server by typing a very long command line in telnet mode.
- Disabled cheats that are based on changing the ship weapon values in the data files.
- Mod files are now stored on www.descent3.com (instead of www.pxo.net).
- Removed support for HEAT.NET, as they're no longer in business.
- Pilot command-line arg (-pilot or +name) is now only checked once, not every time the main menu comes up. This fixes the problem of the game switching back to the pilot specified on the command line after the user has selected a different one.
- When the player's HUD name level is lowered by a game server, the client remembers the higher level and will revert to that level when a server allows.
- Fixed a problem with the GuideBot menu not responding to key presses after firing with the mouse.
- Saved games now properly load custom textures.
- Demos now properly load custom textures.
- Primary weapons no longer behave oddly when attempting to fire secondaries when out of secondaries.
- Fixed a rendering crash that could be caused (among other ways, probably) by a lot of chaff being detonated at once.
- Fixed some (maybe all) multiplayer ghost ship problem.
- Omega cannon energy usage is now not framerate dependent.
- Fixed crashes/slowdowns when using the omega cannon.
- Fixed a problem with the rearview camera when viewing demos of multiplayer games.
- Fixed a ghost ship problem with demos after a player respawned in a multiplayer game.
- Certain objects, such as the surface cannon in level 10, no longer interact with observers in multiplayer games.
- The stats file now contains a listing of team members in Team Anarchy, Mosterball, and Entropy.
- The results screen for team anarchy now shows the team scores.
- Don't show extra teams on team anarchy & monsterball results screens.
- Removed the Mission Status item from the HUD config menu, since there is no Mission Status HUD indicator.
- Removed the missile camera center window option, since it didn't really work (& wasn't supposed to be there in the first place). If you really want the center view, however, you can set MissileView to 1 in the registry. Note that going into the config menu will reset it, though.
- Fixed problems when video bit depth set to 32.
- Clients now can hear the server player taking omega (& other) damage.
- Fixed problems with omega cannon causing wrong amounts of damage and damage to the person firing the weapon.
- Allowed room for longer team names on results screens.
- Ping & packet loss data no longer displayed on HUD in peer-to-peer games.
- It's no longer possible to pick up a powerup in multiplayer while leaving observer mode while moving over the powerup.
- Added confirmation HUD messages when sending private messages.
- Fixed several problems unloading overlay data.
- Made -mission work as described; that is, it now causes the specified mission to start automatically when the game is started.
- Colored stipes now display on player ships in demo playback of multiplayer games.
- HUD gauges now work in demo playback.
- Clarified the description in readme.txt of the -mission command-line option. Refer to Section 7, Command-line Options, for the new description.
- Fixed a couple problems with the level auto-download system.
- In demos of multiplayer games, player ships no longer switch between modesl for different ships.
New features for Version 1.5.0:
- Increased by 20 the maximum number of player ships.
- Increased by 300 the maximum number of textures.
- Increased by 100 the maximum number of objects.
- Increased by 200 the maximum number of polygon models.
- Added "-nosatomega" command-line option to disable alpha effects on omega cannon. Try this if you have speed or crashing problems with the omega under 1.5.
- Added -nocrashbox command-line option to disable the error dialog displayed if the game crashes.
- Improvements for some players using NAT routers. If you're having trouble playing D3 using a NAT, enable port/host forwarding on the NAT server, then specify your port with the the -useport and -pxoport command-line options.
- Added "-datacheck" command-line option. If you get a message on the loading screen that your mission has data errors, use this option and see the file "datacheck.out" for a description of the data errors in your mission.
- In multiplayer, a HUD message is shown when a player's ship is changed because the selected ship is not allowed.
Known issues in Version 1.5.0:
- Because of limitations in the precision of Descent 3's timer, high framerates are not displayed accurately on the HUD.