Article View: alt.games.unreal.tournament
Article #190976Re: First Impressions on UT3
From: GTD
Date: Wed, 21 Nov 2007 22:32
Date: Wed, 21 Nov 2007 22:32
44 lines
3657 bytes
3657 bytes
On Nov 21, 1:15 pm, "skippi" <s...@spam.net> wrote: > Well, basically UT3 is Okay ... but in a lot of ways it's a BIG > disappointment to me. First you should know that I only play Bots, and > mostly I do deathmatch. I don't do online. The Bots are pretty good, so > that's not the problem. > > It's the look - the levels are for the most part dark, dingy and dirty. I > thought it was my card or monitor. Nope! I turned up the brightness and > contrast and details. And where are all the levels anyway. Only about ten or > less for most of the game formats? What's up with that? I guess they are > expecting the user community to fill in the void. By the way, some of the > maps just seem to be all about being fancy, but hardly practical for real > deathmatch. It's like the Epic mappers were just showing off what the engine > could do. Okay. Now release some real deathmatch maps! Pretty please! I hope > there is going to be a major map pack or two or three to make up for all of > this. > > And most of the MODs that come with the game are stupid. After all this time > you would think Epic would know which mutators the gaming community wanted. > Where is instagib? I guess the community has to fill in this void too. So, > why do they charge so much for a half baked game? We should charge them. Ha! > > Now to some technical stuff. Both the Demo and the full game would NOT save > any game configurations!!! Arghhh! (This problem and others are noted on the > Epic game forums.) The solution I used - not found on the forums - was to > edit the game and weapon and engine and player ini files found in > C:\Documents and Settings\XuserX\My Documents\My Games\UT3 ... etc. But, > this is a lot of trouble. So, why did Epic ship with this clearly noted > "bug"??? Oh well, if this is any indication of where Epic is headed, I don't > look forward to Unreal Tournament 4. > > If the mutator and MOD community get on board for UT3, then UT3 will be > great. But, why did Epic do such a half way job on UT3. At least that's what > it look like to me. I'll keep UT3 on my hard drive for a while, but if the > modding and mapping community doesn't get to work then I'll go back to the > other Unreal games for deathmatch botting. > > skippi I agree with you 100%, except I believe Instagib is one of the mutators included. Anyways, You didn't mention the number of bots being maxed at 15, is this an issue to you? It's personally my biggest complaint. .
Technical Details
Message-ID:
<0899b8ae-d860-4660-9844-65c75b1cecc5@v4g2000hsf.googlegroups.com>Path:
mbox-mo1.pugleaf.net!number1.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!postnews.google.com!v4g2000hsf.googlegroups.com!not-for-mailReferences:
<C521j.8035$Rw3.3919@newsfe06.phx>Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!number1.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!postnews.google.com!v4g2000hsf.googlegroups.com!not-for-mail From: GTD <toobiep@yahoo.com> Newsgroups: alt.games.unreal.tournament Subject: Re: First Impressions on UT3 Date: Wed, 21 Nov 2007 14:32:08 -0800 (PST) Organization: http://groups.google.com Lines: 44 Message-ID: <0899b8ae-d860-4660-9844-65c75b1cecc5@v4g2000hsf.googlegroups.com> References: <C521j.8035$Rw3.3919@newsfe06.phx> NNTP-Posting-Host: 146.63.253.183 Mime-Version: 1.0 X-Trace: posting.google.com 1195684331 565 127.0.0.1 (21 Nov 2007 22:32:11 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Wed, 21 Nov 2007 22:32:11 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: v4g2000hsf.googlegroups.com; posting-host=146.63.253.183; posting-account=j8x23QoAAABIxsyjaUzXoILHKdy4J1O6 User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; InfoPath.1),gzip(gfe),gzip(gfe) Bytes: 3709 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit