Free Allegiance Forums

A recently posted KB topic explains how to change the resolution by manually tweaking the registry. It correctly underlines the importance of being very wary when hand modifying the registry.

Well, I built a little app to help change it without touching the registry. Just in case you don't trust putting your hands in there.

You may/will need admin rights, as always.

Download version 0.3 (updated) (68 Kb)

Credits go to All-Api, Documentation staff, Bunnywabbit, aem, Dogbones, Eclipse.

EDIT: Typos.

oh cool /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />

Your app touches the registry instead of the user, to be precise.
That said, this is awesome for us UMPC users with crazy proportions like 800x480.

I did say it's a little app. Nothing special. But you need to begin with little stuff, don't you? /wink.gif" style="vertical-align:middle" emoid=";)" border="0" alt="wink.gif" />

Well I opened it up and was getting errors left and right. Everytime I open it "Error 383 at line 22 in frmMain.frm.Form_Load)." 'Text' property is read-only

Whenever I click Cancel "Error 5 at line 8 in frmMain.frm.Command1_Click" Invalid procedure call or argument.


Hopefully someday I'll learn the DirectX calls necessary to grab the resolutions supported by the graphics device or someone else can code it up. I've tried to find it but haven't found it so far. Allegiance should grab the supported resolutions from each player and have those selectable in game.

I think I got the problem is. The app tries to be smart and automagically sets the resolution in the drop down list to match your windows resolution. This is the resolution you most likely want for a number of reasons. But if the resolution is not found in the drop down list, the assignment fails and an exception is raised. A standard, useless, error handler catches the exception, warns the user and keeps the application alive. VB6 can be so much of a @#(! with error handling...

But enough with technical details. I suggest against downloading the tool until this is fixed and a new version is pushed out - which given the time will happen in around 18/24 hours.

To confirm my theory: aem, what is your Windows resolution?

Thanks!

I think I got the problem is. The app tries to be smart and automagically sets the resolution in the drop down list to match your windows resolution. This is the resolution you most likely want for a number of reasons. But if the resolution is not found in the drop down list, the assignment fails and an exception is raised. A standard, useless, error handler catches the exception, warns the user and keeps the application alive. VB6 can be so much of a @#(! with error handling...

But enough with technical details. The thing is fixed so go grab the new version!

To confirm my theory: aem, what is your Windows resolution?

Thanks!

EDIT: Updated.

badpazzword wrote:QUOTE (badpazzword @ May 29 2007, 06:37 PM) This is the resolution you most likely want for a number of reasons.

I think this is a bad assumption. Given that the info panels do not scale, I for one do not run in full screen mode at the resolution I keep my desktop at 1600x1200 ... I'd need a magnifying glass tapped to my flat panel over the mini-map /doh.gif" style="vertical-align:middle" emoid=":doh:" border="0" alt="doh.gif" />

Lack of scaling is why I'm still running alleg at 800x640. Those boxes are just to darn small otherwise.

Though that may change if I get my PC working through my 28" TV next week!

My resolution is 1272 x 768 because I was never able to get my bargain HDTV to display right at 1280x768 which is its native resolution. It does look excellent, just the 8 pixels on the right side are black but thats not very noticeable.