The VideoBackBuffer should be disabled by default

Bug #896006 reported by LH_Mouse
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ares
Confirmed
Medium
Unassigned

Bug Description

In original YR the video back buffer was enabled by default(until you disable it by adding [Video]\VideoBackBuffer=no in RA2MD.ini). This could obviously slow down the game on modern computers and also invited Internal Errors when the buffer overflowed, so should be disabled by default.

Tags: buffer
Revision history for this message
YR M0ddEr (yr-m0dder) wrote :

It takes one second to add this tag to ra2md.ini and in my opinion, not worth spending time on.

Revision history for this message
Graion Dilach (graiondilach) wrote :

Not to mention that LaunchBase sets this to no per default.

Revision history for this message
Chanterier (speederyr) wrote :

@YR M0ddEr: That could've been said about high res tag as well, which was set to No and changed to Yes in Ares. IMO default settings should provide the best results.

I'm not really familiar with the effects of VideoBackBuffer but if this setting really causes what LH_Mouse wrote in the description, then I'm a supporter of changing the default value for this one as well.

@Graion Dilach: You make it sound as if every Ares user uses LaunchBase as well.

Revision history for this message
Graion Dilach (graiondilach) wrote :

Sorry, I always pair them in my mind, and I didn't know that high-res is enabled in Ares by default. I play RA2 800x600 since 2002.

And yes, I know, I've asked it, MO won't use LaunchBase.

Revision history for this message
WoRmINaToR (worminator) wrote :

I certainly won't vote against changing the default of this, but VideoBackBuffer=yes is one of the most commonly-known causes of lag and VideoBackBuffer=no is one of the most commonly-known fixes to it. Most people who aren't advanced enough to know this fix (or to ask for help when their game lags) probably aren't the people who will be using Ares anyways.

IOW, don't give this priority, but go ahead and change it if you will.

Revision history for this message
DCoder DCoder (dcoder1337) wrote :

We discussed this and decided to change the default right after 0.2, leave it that way for a while to see if any problems occur, and put it into 0.3 if nothing goes wrong.

Revision history for this message
WoRmINaToR (worminator) wrote :

no objections.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.