Tiny small bug

Tiger · Post by **Tiger** » Mon Jun 15, 2009 9:31 am

Hi

(still here)

Just got a new 22" 16:9 monitor the other day, and fired up legends, looked awful at the old res, so I let it use optimised settings, reduced reflections, and background nebulas, low detail, and wanting to squeeze every extra frame per second, reduced the coloor setting to 16 bit.

On luanching, at about 10% loading, the program crashed.

On resetting the colour setting to 32 bit, no crash.

Desktop res is now 1680 * 1050 with 32 bit colour, so don't know if there was a conflict here.

I've tried other resolutions for Legends, and they just don't look good any more.

Framerte isn't bad on my machine, but I was wondering, whats best no cockpit, strutless cockpit, or full cockpit for framerate?

Chris

warsign · Post by **warsign** » Mon Jun 15, 2009 9:38 am

I play with 22 and bigger monitors, optimized settings and custom settings, antialiasing on and game looks awesome.

Problem might be related to your GPU and OS.
You have to check out your GPU divers and Direct X may be.

Tiger · Post by **Tiger** » Mon Jun 15, 2009 11:19 am

Hi

Yeah, all up to date, but you're right it is a bit of an aging computer (holds breath, 2003 ish)

The issue wasn't with speed (its a given its going to be a little slow), the issue was going from 32 bit to 16 bit colour and getting a creas, then going back to 32 bit and getting no crash.

Chris

Maarschalk · Post by **Maarschalk** » Mon Jun 15, 2009 11:59 am

Evochron Legends does not work with 16bit color resolution. Only uses 32 bit!;)

Post by **Vice** » Mon Jun 15, 2009 5:01 pm

16-bit may indeed not be fully compatible with some configurations, or at least in some modes on some configurations. It's a legacy option more intended for testing purposes, you probably won't get much of a performance improvement by using 16-bit anyway, best to stick with 32-bit unless you need to use 16-bit for some reason.

Framerte isn't bad on my machine, but I was wondering, whats best no cockpit, strutless cockpit, or full cockpit for framerate?

Fewer polyogons generally equates to a better framerate, so no cockpit would provide the most benefit. Removing the struts is more for just visual preference, it doesn't reduce the polygon count much.

Maarschalk · Post by **Maarschalk** » Mon Jun 15, 2009 6:15 pm

How much of a framerate increase does no cockpit translate in to, 20%?

I can try it out, but I want to know what is normal, that is how much increase should I expect?

Post by **Vice** » Mon Jun 15, 2009 6:41 pm

Depends on the system, some may see an improvement of only 1 or 2 fps, some may see an improvements of 10-15. More powerful systems generally see less of an improvements as they can typically render more polygons in a scene simultaneously with less of a performance hit.

Maarschalk · Post by **Maarschalk** » Mon Jun 15, 2009 8:22 pm

Thanks for the info Vice!;););)

Wasp89 · Post by **Wasp89** » Mon Jun 15, 2009 10:21 pm

I actually see a marked framerate increase with just the struts turned off.