Olcfg.exe Application Error

[Verline Wesolowski]

OLCFGEXE problems are generally seen during Sampler Includes Previews of Titles from these companies: program launch, and typically caused by executable file corruption, or in some cases if the file has been accidentally or maliciously removed by malware. Downloading and replacing your EXE file can fix the problem in most cases. In addition, if your OLCFG.EXE error was due to a removed malware infection, we recommend running a registry scan to clean up any invalid file path references created by the malicious program.

Although the majority of error OLCFG.EXE messages will be solved if the file is placed in the correct file location on your hard drive, you should run a quick test to be sure. You can test the result by running Sampler Includes Previews of Titles from these companies: application and seeing if the issue still appears.

Usually OLCFG.EXE errors with Sampler Includes Previews of Titles from these companies: happen during startup or shutdown, while OLCFG.EXE related programs are running, or rarely during the OS update sequence. Notating when OLCFG.EXE errors occur is paramount in finding the cause of the Sampler Includes Previews of Titles from these companies: problems and reporting them to Hasbro Interactive Inc. for help.

Outlaws seems to drop some inputs. Writing cheat codes (olpostal and olscore are two) or exiting the game (you're supposed to be able to press esc to skip the credits) are good ways to test, just standard playing should make the problem obvious at times too.

DXGL does not have the same problem. This is for the DirectDraw renderer, The problem also applies to the Direct3D render, but I can't compare with anything since dgVoodoo2 is the only way the Direct3D render works on a modern computer).

This only happens in emulated modes (windowed and dgVoodoo2's own scaling modes), I can't actually get unemulated modes to work because Outlaws does something weird that forces dgVoodoo2 into windowed mode.

There is a known issue with the mouse: unusable with 'scale, keep AR' scaling modes. The mouse cursor is locked to the upper left corner.

I know what the problem is, I just don't know how to fix it without a new CPL option.

Yes, the game quits with an error message if Glide renderer is chosen.

This is a bug in dgVoodoo, in cooperating between DDraw and Glide, I fixed it. (Native DDraw + dgVoodoo Glide may work, I didn't check it.)

(As a side note, for the Glide renderer, Voodoo2 or earlier 3Dfx card must be selected in the CPL because the game assumes tiled videocard memory (2048 byte wide) and it otherwise crashes when trying to display the in-game menu in response to pressing Esc.)

I cannot skip the credits, it's true...

What is interesting, it all is independent on the renderer type (Glide, DDraw, D3D) and the scaling mode. Unemulated modes works for me.

Capturing the mouse however is not applied (it's a bug...) but in turn, the mouse cursor is fully usable for accessing the menu items, so it's a good bug after all... ?

I remember having a font issue in directx mode via dgVoodoo in Outlaws GOG version. The messages in the top left corner of the screen were very small and illegible via dgVoodoo. Glide mode via nGlide did not have the font problem.

Controls seem to be fine, but it has another issue.

If forced res + forced msaa is used then menu items become black squares, it's a regression but because it worked fine with 2.53.

I want to fix it anyway.

Also, there is another issue: with emulated stretching modes, forced res the mouse cursor (game menu) doesn't move because never gets redrawn, only when the selection moves from one menu item to another.

The same issue with Settlers III.

I'd like to fix it too, somehow.

Yes, indeed, I checked it.

Whiteness is position and view angle dependent though, I can position myself to get the waterfall to appear as it should.

Glide renderer is OK.

I'll check the reason later.

The game creates 2 textures for the waterfall and one of them is released right after it created and loaded with bitmap data.

Later, when choosing which one to render, the texture is not found by its associated texture handle, so whiteness is symptom of a missing texture.

It very seems to be an Outlaws-D3D renderer bug. BTW, I never thought that D3D renderer of Outlaws is D3D2. Good old execute buffers... ?

I knew Outlaws' Glide and D3D renderers were just post-support patches and probably not all that good, but I'm surprised they left a so huge problem, but you're right I just checked the D3D patch notes:

To get the Glide renderer working with dgVoodoo2, you need to copy the DLL files from both the 3Dfx and MS folders in the dgVoodoo2 distribution. I didn't really see any benefit to that over nGlide, though.

You need to choose a lower resolution in olcfg.exe. Choose 640x480 for the text to be the size that it was designed. That won't actually be the resolution that the game engine runs in. The 3D engine will use the resolution that you force in dgVoodoo's control panel and the 2D overlays will use the resolution set in olcfg.exe. It's a bit weird, but that's the case. As for the illegibility, I found that that was caused by Render overlays in 3d acceleration in olcfg.exe->Direct 3D->Advanced. De-select that.

The advantage is: if you don't mind messing with Borderless Gaming and changing resolution before you start the game then dgVoodoo2 can offer instant transitions between cinematics/menus and gameplay. DXGL+nGlide can do pretty good transitions too, but not as perfect as dgVoodoo2 in windowed mode.

You need to choose a lower resolution in olcfg.exe. Choose 640x480 for the text to be the size that it was designed. That won't actually be the resolution that the game engine runs in. The 3D engine will use the resolution that you force in dgVoodoo's control panel and the 2D overlays will use the resolution set in olcfg.exe. It's a bit weird, but that's the case.

Outlaws actually does some 3D correction in higher resolutions that forcing resolution via dgVoodoo2 (or nGlide) won't replicate. Being able to run in higher resolutions is the main advantage of Direct3D mode. If you set Outlaws to 640x480 and force resolution you might as well use the Glide render (which has no ugly waterfall glitches).

That, I do, and you need to be a little more appreciative when someone's simply eager to help you. I even offered a potential solution for an issue that you didn't get an answer for, and that got ignored. I don't "need" to try to help.

OK, sorry for wasting your time, I should have actually mentioned that the bug I ran into was fixed in the latest dgVoodoo2 and that the mouse cursor missing was an notice for Dege not something I can't figure out how to work around myself (I use a utility called nomousy). If there's many games with such issues Dege might want to consider fixing it.

So I just tried Outlaws in newer DXGL versions and waterfalls work just fine. Chances are if they work fine in DXGL, there was graphic hardware they worked properly with which is why the Direct3D render shipped with the bug. More importantly it means waterfalls can work in the Direct3D render. So can you fix it? Pretty please? It's all that's remaining to make Outlaws work perfectly with no compromises.

The thing is, I can't fix it. Last time I debugged it, it revealed that the (game) renderer releases (destroys) some of its textures before they get rendered.

Isn't it a bug in DXGL instead? I mean, DXGL may not release the texture objects when they should be released and so it works only by chance?

BTW, unfortunately I don't have an AMD card at all by now. But I see that AMD texturing problem is a growing issue.

I'd need some little app (a scene demo maybe) that it can be reproduced with, and send it to the AMD bugreport system.

There are plenty of occasions when you will find that Microsoft Office 2016 applications may crash or cannot start. You hook up to the net to find a solution and there are many articles around such issues from Microsoft or others. However, every case is very different and there is no one rule to solve them. The same happened to us and we thought a discussion of such a particular case could be helpful to others since we did not find any ready reference for a quick remedy for the issue we faced.

After update to Windows 10 Pro (64-bit) build number 19041.388, Outlook has been refusing to start up. All the other Office applications work without error. Only Outlook closes automatically every time it is started.

You will of course go frantic if you suddenly find your Outlook is not working after you have done a legitimate update. And chances are you will be looking through the maze of different references available before you hit upon the one that works for you. Our bid is to help the users under the said circumstances and get back to feet quickly.

3a8082e126