Games crashing with WindowBlinds running.

It's going to be a bummer if I have to unload WindowBlinds each time I want to play a game.

I have 50 or 60 games installed...none have that issue...but if necessary you can always exclude WB from skinning [or attempting to skin] your 'Bloodrayne 2'.....no need to exit WB at all...

Ok, so how do I do that? I'm a rookie here, just got this program a couple of days ago. And why would this program try to skin a game? That doesn't make much sense.

Windowblinds Configuration - Settings - Per Application - Add per application setting - browse to game executable - click 'open' and in resulting window select "Total Exclusion" [Ignore this application and do not skin it].

Done...

it skins a game because from a programming standpoint, they would need a list of applications that are games and those that aren't games in order to determine what to skin or not to skin. doing this would result in unnecessary maintenance (adding/changing programs in the list), and many apps not being skinned or being skinned regardless of what they are because they aren't on the list. now THAT doesn't make much sense.

WB shouldn't try skinning anything that goes full screen anyway.  At least that's how I would have programmed it.  SD leaves too many holes to be filled in by the end user.  If you ask me it's just attention to detail and innovation on resolving potential problems before the end user sees it that's lacking here.

SD leaves too many holes to be filled in by the end user. If you ask me it's just attention to detail and innovation on resolving potential problems before the end user sees it that's lacking here.

Maybe I should count them....hang on... 34 FULL games....31 demos....that's 65 titles in total...not one requires exclusion from Windowblinds.

Put another way....for the mathematically challenged...that's a 100% success rate.

No failures.

No 'holes'....

Simplest game is probably Fury3D ....more 'complex'...Doom3...Quake4...UT2004...'biggest' [at currently at 17,092 files and 4.93 GIG is GTR [on 147 separate racetracks].

Maybe I'm just lucky...or maybe WB is actually quite good...

 

My UT2004 folder is currently 12.9 gig... ***raspberry***

At least that's how I would have programmed it.

Then why don't you go get on that instead of talking out your ass. Your know it all griping has received nothing but polite attempts to help--stymied only by the fact that every suggestion must be wrong because you know better.

If you ask me it's just...resolving potential problems before the end user sees it that's lacking here.

Well, unlike you, I'll bet Mike089 actually considers and tries out the exclusion suggestion given above. And, if you can take a moment to think this through (which seems doubtful) then you will see that the mechanism for application exclusion built into Windowblinds and readily available to anyone who uses it IS "resolving potential problems".


Seriously. If you want to constructively criticize something, you can do it in your own thread. But hijacking others' threads with your insipid, uninformed, unlikely (I personally doubt you could program the path out of a paper bag), irrelevant non-sequitur gripes is the kind of thing that might get you flamed.

JRSCCivic98: Your posts are not helpful in anyway to the user.

WB5 does detect full screen DX and OpenGL apps, but in this case it sounds like another app has taken focus and this has caused the game to switch out of full screen mode.  The resulting crash when going back to full screen is probably a bug in the game itself (so many games are unable to handle switching)

Hey, all my games work too... that's not the point.  The point is this.  Between 3 PCs that I've tested the latest version of WB5 they all exibit different issues.  So, it seems to me that different hardware configurations (same OS) play a big role on what's exposed in WB5's bag of bug tricks.  Everyone gripes about everything... get over it... it's life.  A good aspect on how things should be layed out lies in knowing how to properly place all of your dominos so that you've got as many possible (user variables) covered... the way you complete that path from start to end is up to you programmers.  I'm just stating that while you know the limitations of your program and what not to do.... ALWAYS expect the user to try ANYTHING.  It is this simple fact that causes bugs to start surfacing.  When programmers test things inhouse they know the overall correct things to do in a program.  It's not until a user tries to do something "off the wall" (which the programmer would never constitute as logical) that things start to break.  Use this logic and there would be less griping I think.  Just a suggestion of logic of course.  Good day.

Everyone gripes about everything... get over it... it's life.

Not 'quite' true.  Some people have more tolerance, even acquiescence.  Some don't glibly quip 'get over it'.  So it's not necessarily 'life', at least not for everyone.

There's no necessity to migrate your litany of issues to an unrelated thread.  The issue here was a game which did not behave well with WB [and it should be noted that is not necessarily a WB issue but actually/probably a game issue....were it truly a WB issue I, for example would not have 65 games co-existing happily with it].

A solution [exclusion] was suggested.

An explanation of potential cause was delivered by the program's coder.

So it seems your input may really have been of zero value/relevance...."that's life, get over it"....

So it seems your input may really have been of zero value/relevance...."that's life, get over it"....

Yep... from some of your posts right after mine in multiple threads... the same is true.  You said it.