Bug 1485 - Importing of map CTF-DE-LavaGiant2 fails
Status: RESOLVED DUPLICATE of bug 1425
Alias: None
Product: Unreal Tournament 2004
Classification: Unclassified
Component: client
Version: 3186 (Initial retail version)
Hardware: PC Linux
: P2 normal
Assignee: Ryan C. Gordon
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2004-03-25 05:55 EST by Oliver Feiler
Modified: 2004-04-04 05:59:07 EDT
0 users

See Also:


Attachments
log for first launch (4.35 KB, text/plain)
2004-03-25 05:56 EST, Oliver Feiler
log for second launch (7.00 KB, text/plain)
2004-03-25 05:57 EST, Oliver Feiler

Description Oliver Feiler 2004-03-25 05:55:31 EST
I was importing some maps from UT2003 into 2004. From what I heard it should
work just fine and it worked with all but one.

If I copy CTF-DE-LavaGiant2 from the original Digital Extremes bonus pack to the
Maps folder the following happens.

First startup after copying the map:
------
$ ut2004
Exporting CTF-DE-LavaGiant2.....Successful!
WARNING: ALC_EXT_capture is subject to change!
------

Game launches fine and the map works.

Exit and restart again:
------
$ ut2004
Exporting AS-Convoy.....Successful!
Exporting AS-FallenCity.....Successful!

[...] Every existing map seems to get exported now.

Exporting TUT-DOM2.....Successful!
Exporting TUT-ONS.....Successful!
Exporting CTF-DE-LavaGiant2.....Successful!
WARNING: ALC_EXT_capture is subject to change!
_X11TransSocketOpen: socket() failed for local
_X11TransSocketOpenCOTSClient: Unable to open socket for local
_X11TransOpen: transport open failed for local/kiza.lan:0
Couldn't set video mode: Could not create GL context


History:

Exiting due to error
------

The game leaves a file CacheRecords.ucl in ~/.ut2004/System that was not there
after the previous launch and it doesn't seem to start anymore until I delete
that file and the map from System/Maps.

It seems like a pretty weird error that "set video mode" fails. I'll attach the
logs from first and second launch. They don't really contain many useful things
afaict.

I'm using Nvidia's 5336 drivers, but if that's a driver bug, it's pretty weird.
Comment 1 Oliver Feiler 2004-03-25 05:56:40 EST
Created attachment 268 [details]
log for first launch
Comment 2 Oliver Feiler 2004-03-25 05:57:07 EST
Created attachment 269 [details]
log for second launch
Comment 3 Ryan C. Gordon 2004-04-04 05:59:07 EDT

*** This bug has been marked as a duplicate of 1425 ***