Outcome?

[Guest]

A mention (for example in the availability table notes) would be nice, especially to tell the reader whether he could use Outcome, just patch .par, or even better the game is DRM free

That'd make the pages as bloated as putting the UE3-specific method for skipping intro movies (see http://pcgamingwiki.com/wiki/Engine:Unreal_Engine_3#Skip_intro_videos ) directly on every game article. Since Outcome works in general on games which require Origin to launch - which, BTW, vanilla Battlefield 3 does (see http://pcgamingwiki.com/wiki/Battlefield_3 ) - just pass a link on the game article to the appropriate section of the Origin article like I did for the similar Buddah engine method (see http://pcgamingwiki.com/wiki/Costume_Quest#Issues_fixed ).

 

Though, you can't just throw it in the Origin page.

Someone once said a similar thing about universal and engine-specific fixes and improvements; I talked with Soeb and he cleared it - to the point of mentioning he'd be adding it to the official editing guide once it went live (see http://dev.pcgamingwiki.com/wiki/Borderlands_2#Issues_fixed for example syntax).

Edited August 26, 2015 by Expack3

[Guest]

That'd make the pages as bloated as putting the UE3-specific method for skipping intro movies (see http://pcgamingwiki.com/wiki/Engine:Unreal_Engine_3#Skip_intro_videos)directly on every game page. Since said fix works in general on games made with UE3, just pass a link to the page like I did for the similar Buddah engine method (see http://pcgamingwiki.com/wiki/Costume_Quest#Issues_fixed).

I always forget about that page. It doesn't work for all UE3 games though, there are some cases in which other parameters are required.

[Guest]

I always forget about that page. It doesn't work for all UE3 games though, there are some cases in which other parameters are required.

That's why the "in general" part - there will always be exceptions, and those are the ones where stating the "no intro videos" enhancement for that game isn't redundant, but useful.

[Mirh 103]

That'd make the pages as bloated as putting the UE3-specific method for skipping intro movies (see http://pcgamingwiki.com/wiki/Engine:Unreal_Engine_3#Skip_intro_videos ) directly on every game article. Since Outcome works in general on games which require Origin to launch - which, BTW, vanilla Battlefield 3 does (see http://pcgamingwiki.com/wiki/Battlefield_3 ) - just pass a link on the game article to the appropriate section of the Origin article like I did for the similar Buddah engine method (see http://pcgamingwiki.com/wiki/Costume_Quest#Issues_fixed ).

Absolutely not.

First of all, you can't expect people to check engine page.

Second, skip intro videos.. bloat? No, I don't think so. Especially considering that the space required for an ideal "check engine: page" would be the same of an ideal 1 line fixbox.

Third and above all, in general doesn't mean really much imo, considering at least in my experience, only once that command worked (perhaps it's reversed for you, but that could only prove the claim is questionable at most imo)

 

Speaking of Outcome, specifically, you are doing exactly the kind of misunderstanding that I was trying to rule off in my previous post. Battlefield 3 requires Origin in the sense that a .par file tell him: hey, check for origin, because.. whatever. But technically it does nothing with it.

Battlefield 4 on the other hand requires Origin in the sense that it perform some things that aren't explained, but that actually make requiring Origin meaningful.

And this is what Outcome try to replace.

So you see that behind the same event, different situations can be the cause.

 

A little mention (with a link) in the availability table notes section doesn't seem insane (considering we have such things)

Whether this should point out to engine page or other information section is a bit more shady.

Though, I remember you that common fixes are there when the procedure is the same with every one. 

Already if the executable/par is not in {{p|game}} you should mention where it is..

 

Someone once said a similar thing about universal and engine-specific fixes and improvements; I talked with Soeb and he cleared it - to the point of mentioning he'd be adding it to the official editing guide once it went live (see http://dev.pcgamingwiki.com/wiki/Borderlands_2#Issues_fixed for example syntax).

Having general troubleshooting guide there is something I every desired since.. well, since I'm here.

But that is for things that (causes problems and) are given for granted.

You don't give a command line parameter for granted.

 

Engine pages (or, for example, sound page) on the other hand are either for:

• reference in the case there's a new bugged game we haven't covered that somebody would like to check with broad-spectrum fixes
• there's a common problem that has always the same solution

Note that the best way to talk of smoothing framerate, imo, would be to make a fixbox explaining where to look for ini entries and all, and then linking all the massive digression that covers every need.

[Mirh 103]

Yes but.. I don't see any mention in Origin page.

[Garrett 214]

I have added a basic mention to the Origin page (under other information since this is not essential nor specified as a solution for a specific issue).

[Mars icecream 57]

The same author has Origin Requirement Remover tool available: http://par.nofate.me

It doesn't seem to crack the games, only removes Origin requirement after initial EA account sign in. Worked with every game I tested.

[Mirh 103]

The same author has Origin Requirement Remover tool available: http://par.nofate.me

It doesn't seem to crack the games, only removes Origin requirement after initial EA account sign in. Worked with every game I tested.

http://blog.nofate.me/?p=35