Widescreen Gaming Forum

Nice, i was thinking to do a report by myself, but now i will download the demo and look if i can run it on my natve resolution (1680x1050 :) )

Go EA go. :lol:

Maybe something usefull

To play Nod in skirmish game

Start skirmish game
Where you can chose between nod and gdi press N
Press by opponent G

For different tactics you only have to press the type, so for a rushing enemy press R

source

Something more usefull is

==================================================================

Command Line Parameters

==================================================================

The Command & Conquer 3 Tiberium Wars Demo supports several

command line parameters that may give you increased flexibility in

the way that you run the game. To set a command line parameter,

you need to do the following:

1. Go to the location of the game's executable. This is

typically found in C:Program FilesEA GamesCommand & Conquer 3

Tiberium Wars DemoCNC3Demo.exe.

2. Right-click on the CNC3Demo.exe icon and select "Create

Shortcut".

3. This will create a shortcut of the executable within the same

folder. This will typically be called "Shortcut to

CNC3Demo.exe".

4. Right-click on this new shortcut and select "Properties".

5. Add a space to the end of the string in the "Target:" field,

followed by a "-" and then the command line parameter.

The following command line parameters are supported by Command

& Conquer 3:

-noaudio (Launches the game without any audio)

-xres (Forces the game to a specific horizontal resolution)

-yres (Forces the game to a specific vertical resolution)

Source

I haven't forgotten this. There are just a few things I'd like to see for myself, and download speeds for the demo aren't exactly blazingly fast for a 1.2GB file. I swear, it feels like entire game installation sizes were smaller than that just yesterday.

*downloads 84MB demo for Sam & Max Ep4 in 15 minutes and finishes it in 5*

Can confirm 16x10.

I'm impressed with EA for this :)

Yeah I know what you mean Cranky. I had to leave my computer running over night to get the demo because I didn't want to wait around for it during the day. :P

Also those command lines are interesting, I'll try to get 1280x768 working like that.

Edit: Ok it works... editing the report.

I've played the demo, and I've seen what I want to. However, this game has a case that the system doesn't yet resolve - all of the resolutions work natively EXCEPT for 1280x768 (I tested them all, including 1680x1050, 1920x1080, and 1920x1200). 1280x768 users must use the command line solution. I'll get back to this in a day or two, I want to hear some "insider" opinions on how to handle this.

FYI on the aspect ratio, I found that everything wider than 16:10 is vert - compared to it. The wider the aspect ratio, the

Also, here are a few superimposition shots of my own. In all of these shots, widescreen is black & white, and 4:3 is in color.

First, 4:3 on 16:10:


This shows that the FOV is overshot, and by a lot.

Next, 4:3 on 16:9:


Here, the FOV is still overshot, but not by as much.

Last, 4:3 on 3:1:


At this point it is both hor + and vert -, but the hor + gain is higher than the vert - loss. I estimate that at 4:1, they would be roughly equal.

Finally, here's thumbnails of the 4:3 and 3:1 images. Something tells me that Ibrin would want them.

Yeah there is quite alot of extra FOV for 16:10 resolutions.
It seems they may of worked more to get the 16:9 FOV correct, even though it still is slighty vert+ compared to 4:3.
They have added more to the top and bottom for 16:10 rather then cutting back the sides.
I guess its better then Vert-... but its not quite right.

I just discovered another thing. If you compare 5:4 and 16:9, the 16:9 shot is almost exactly hor +.




I have a hypothesis about how this works. EA has chosen two FOV baselines - one for standard, and one for widescreen. The standard baseline is actually optimized for 5:4, not 4:3. The widescreen baseline is optimized for 16:9. Therefore, when you use a 4:3 resolution, you are getting an FOV that is too small, and when you use a 16:10 resolution, you are getting an FOV that is too big.

If we assume that the FOV at 5:4 is just right and the FOV at 16:10 is too big, we can approximate how "too big" 16:10 is with a 5:4 on 16:10 shot.



Going by this, the FOV overshoot isn't quite as big.

Now for the grade. The general consensus is that the manual solution for 1280x768 should be considered a minor singleplayer anomaly. I would go with this for the time being - if someone objects strongly enough to cause the general consensus to change, I'll come back to this and let you know what happened.

Also, I consider the FOV overshoot at 16:10 to be another singleplayer anomaly.

==Grading==

Calculated grade: B+

Major unresolved issues: None
Minor unresolved issues: None

Summary of widescreen-related flaws:
FOV overshoot on 16:10 resolutions
Manual solution for 1280x768

Cranky's coverage estimate: 100%