View Issue Details

IDProjectCategoryView StatusLast Update
0001109FSSCP---------public2008-10-21 02:11
Reportermartellato Assigned Totaylor  
PrioritynormalSeveritytrivialReproducibilityalways
Status resolvedResolutionunable to reproduce 
PlatformPCOSWindows XP ProfessionalOS VersionSP2
Product Version3.6.9 
Summary0001109: "Failed to set graphics mode" error when connected by Remote Desktop
DescriptionIn the circumstance that you decide to launch a standalone server while connected to the serving machine via remote desktop, you receive a "Failed to set graphics mode" error. This is VERY trivial, seeing as once you hit Ok, the standalone launches and operates normally.
Steps To Reproduce1. Connected via remote desktop to the serving machine
2. Launched with command args:
C:\Games\FreeSpace2\fs2_open_3_6_9_rc7dot8_debug.exe -standalone -multilog
TagsNo tags attached.

Activities

taylor

2006-10-18 23:10

administrator   ~0006904

What is the exact error message?

I've looked for "Failed to set graphics mode", and variations, but haven't found anything so far. I'm not sure that this is actually a game error which is why I ask.

taylor

2006-11-15 01:00

administrator   ~0007127

* BUMP *

Any more info on what the exact error message was? There is nothing I can think to do about this until it's known what was generating the error.

Goober5000

2007-02-22 00:36

administrator   ~0007695

I've encountered this issue before (though while trying to launch FS2, not a standalone server). I'll try to get the message this evening.

phreak

2007-02-22 06:36

developer   ~0007697

i believe remote desktop uses the default svga graphics driver, i couldn't even remote into home and start up starcraft. It said i needed to install DirectX 5.

Although the standalone should just pass up all graphics checks anyway.

Goober5000

2007-02-28 07:19

administrator   ~0007758

Bah. I can't get Remote Desktop to work here. :(

taylor

2008-07-17 16:26

administrator   ~0009455

Not going to work on this.

taylor

2008-10-20 02:08

administrator   ~0010051

This isn't really specific to multiplayer, not is it an error from the game itself. This is mostly likely a Windows specific error message, though from what I have no idea. I'm going to try and replicate it in the next day or two and if I can't then this bug will just be closed.

Issue History

Date Modified Username Field Change
2006-10-11 23:21 martellato New Issue
2006-10-18 23:10 taylor Note Added: 0006904
2006-11-15 01:00 taylor Note Added: 0007127
2007-02-22 00:36 Goober5000 Note Added: 0007695
2007-02-22 06:36 phreak Note Added: 0007697
2007-02-28 07:19 Goober5000 Note Added: 0007758
2008-07-17 16:26 taylor Note Added: 0009455
2008-07-17 16:26 taylor Assigned To taylor =>
2008-07-17 16:26 taylor Status assigned => new
2008-10-20 02:08 taylor Note Added: 0010051
2008-10-20 02:08 taylor Category multiplayer => ---------
2008-10-21 02:11 taylor Status new => resolved
2008-10-21 02:11 taylor Resolution open => unable to reproduce
2008-10-21 02:11 taylor Assigned To => taylor