The Champions Online launcher keeps crashing right as I start it. I have reinstalled Champions Online numerous times, and i know the installation works because i installed it on another computer and it works just fine. I have completely updated Windows XP and Direct X. I also am sure my computer fits the system requirements. Yet the launcher continues to crash.
do you get any crash error message? in the game directory there are error and crash.log what are the last few line in those logs? can you post a dxdaig report?
It says to send a crash report to help them figure out what is wrong. The error ticket ID: comes up as unknown unless i turn off McAfee. Even with McAfee turned off, when i hit submit, nothing else happens, and the ticket is closed and seems as if deleted. And how do i get to the crash logs?
100113 02:06:06 1 MasterControlProgram[1]: OLE failed to initialize: 1
100113 02:06:06 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 1"
100113 04:14:27 1 MasterControlProgram[1]: OLE failed to initialize: 1
100113 04:14:27 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 1"
ok and i found the dxdiag but what do i post from it?
I am getting the very same error, both in CO and in STO. Sometimes CO gets to the screen where you are supposed to press the play button but when I do nothing happens.
Oddly enough I am getting an error similar to this one.
For some reason the launcher is crashing whenever it tries to patch CO. And it also crashes when I try to patch STO.
You hardware looks to be ok. I not sure what the latest driver for the ATI is but I would try uninstalling the driver. reboot to safe mode use a driver removal type program (there is a couple out there and people have thier preferance) to remove any lingering driver files. then install the latest driver.
cousins100
you should start a new thread instead of necro one a year old. post a dxdiag report of your system but basicly it looks like your video card or driver is unable to support the game.
repair the error on my pc, what you should do is close the launcher, then use ccleaner to clean all the records, because it is a problem in the records, that I read in other forums, once cleansed records of your PC, open the launcher and it works ...
repair the error on my pc, what you should do is close the launcher, then use ccleaner to clean all the records, because it is a problem in the records, that I read in other forums, once cleansed records of your PC, open the launcher and it works ...
is there anyone experiencing the auto aupdater of the launcher,if does can pls help,mine is taking forever to update...its trying to cennect 30 times and more but the launcher still does nor pop out...is there any connection on mcaffe?i accidentally press the block button and is started like this....can any one help me about this??? pls....
Interesting, some sort of Direct 3D error it seems. Doing my best to look into this, but not the easiest thing to pin down. I read something about another game where someone had to manually edit a config file (usually a text file in your game folder).
So perhaps you can try the following?
Only start the game in fullscreen, at a low resolution, only one active monitor, disable any crossfire or sli ....I can't gaurantee any of this, but could worth a try. I'll keep looking around the web for related errors.
I'm getting the same crap and after reading this thread it looks like I am **** out of luck...Anybody with some sort of tech background able to answer wtf is going on? Or should we just uninstall and forget these "free" games?
and i know the installation works because i installed it on another computer and it works just fine.
Hello LoneWolf217,
From your statement above, you prove that the install is fine, however, you also prove that the "issue" is indeed related to the computer to which you're having issues with. In a nutshell, it's the computer, not the software we're dealing with.
That being said, This error is directly related to your C++ OLE Library. In essence, it's broke. You see, the computer uses .dll files as road signs if you will. When you double click on a shortcut on your desktop, like say Outlook so that you can access your email, the computer sends a request to the CPU to launch Outlook. In a perfect world, Outlook would launch and you'd be able to go about your business as usual. However, when you have a broken .dll file, 3 things can occur:
Nothing happens
A totally different program is accessed
Or you get an error message
In this case, you're getting the error message as referenced by your following post:
100113 02:06:06 1 MasterControlProgram[1]: OLE failed to initialize: 1
100113 02:06:06 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 1"
100113 04:14:27 1 MasterControlProgram[1]: OLE failed to initialize: 1
100113 04:14:27 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 1"
ok and i found the dxdiag but what do i post from it?
Naturally, dxdiag and DirectX in general have nothing to do with this issue. This is all related to your C++ OLE Library.
How does this happen? Good question! Sadly, there's a multitude of different reasons why this might happen. One of the most common reasons is that your OS is corrupted. OS Corruption occurs when the user(s) doesn't regularly conduct computer maintenance, such as deleting temporary files and things like this.
How do I fix my OS? Another good question, however the answer isn't one that most folks like to hear, much less consider, which is of course; Reformat.
Now, I'm not the type of person to simply go, hey man, your stuff is broke, reformat, unfortunately this issue doesn't really allow for much elbow room if you will, thus the quickest and easiest method is to reformat.
My suggestion: If you can, backup your sensitive data to a removable harddrive and reformat. If you don't have anything worth saving, go ahead with the reformat. Reinstall XP and go from there.
If you'd like to learn more about the C++ OLE Runtime Library, please see these pages on Microsoft.com:
Time of this report: 1/12/2010, 20:07:31
Machine name: KREVIN-NINO
Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.090804-1435)
Language: English (Regional Setting: English)
System Manufacturer: BIOSTAR Group
System Model: TF720 A2+
BIOS: Default System BIOS
Processor: AMD Phenom(tm) 9950 Quad-Core Processor, MMX, 3DNow (4 CPUs), ~2.6GHz
Memory: 3328MB RAM
Page File: 928MB used, 4282MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.5512 32bit Unicode
I can see that you do have some corruption going on here, unless of course you don't know how to set your clock in Windows. As you can see from the report above, your computer thinks that the date of process of this report was in fact 1/12/2010, 20:07:31 which we all know is not correct, unless of course you didn't do the report recently, which I doubt. That of course brings me back to OS corruption.
Another item of note is that your version of DirectX isn't up to snuff. You might want to update DirectX from Microsoft.com and attempt to launch once again, however, I really doubt that will fix your issue. I also took the liberty of bolding your Service Pack information from your quote above. I've never, ever advocated for any of my customers to update their XP beyond SP 2. There are many reasons why but the most important one is the simple fact that XP SP 2 is not only stable, but exceptionally robust. In laymans terms: SP 1 sucks, SP 3 sucks, SP 2 good. Sadly, the only way to "go back" to a previous Service Pack is not to uninstall it, but to reformat and not update past SP 2. I don't care what anyone says, sure you can "uninstall" SP 3, but it will not revert back to SP 2 without leaving a bunch of unwanted, craptacular files from SP 3 on there which of course interfere with the standard operations of the computer itself. This will of course lead to OS corruption.
I'm sorry to be the bearer of bad news my friend, however there's no real "nice" way to put this.
Best of luck and I really hope that my post has helped you out in one way or another.
I can see that you do have some corruption going on here, unless of course you don't know how to set your clock in Windows. As you can see from the report above, your computer thinks that the date of process of this report was in fact 1/12/2010, 20:07:31 which we all know is
The Day they posted their original post!
You've been at this too long. Get back to the game and relax.
We bring up a dead thread cuz in the past 2 years not a single person has been able to figure out this issue...2 years of time to research this issue and no answer = fail in anybodys book. Then I go to STO forums and get a fix within one day. If you are running Teamviewer, unistall it. The End.
look guys ,i have an error on champions online.i created the character and when i was ready to play it stopted loading.my error id is 14196834.i reinstalled the game but it doesnt work.please help me!!!!!!
same problem, was fine before the recent patch.
once i hit play, screen enlarges and goes black, then cryptic error comes up...
close with task manager, start again, it asks me if i want to verify ..
my wife sat next to me has no problems running it..
but like i say, before the patch it was fine.
If you use DisplayFusion -- you will need to go through he steps int he link as this fixed it for me!
This was my exact problem. I don't run Teamviewer but I do run Display Fusion. I uninstalled and reinstalled, no luck. Clicked and unclicked every possible combination of checkboxes in the Options of the launcher.
If you run Display Fusion you must do the following.
Right click the DisplayFusion icon in your system tray and pick settings.
Go to the Compatibility tab.
Click Add
Add both \Users\Public\Games\Cryptic Studios\CrypticError.exe
and \Users\Public\Games\Cryptic Studios\ChampionsOnline.exe
(adjust the path as necessary)
Uncheck all the all the boxes.
And OK your way out of it.
CO should run fine with DisplayFusion after that.
Comments
100113 01:46:20 1 MasterControlProgram[1]: Shutting down: C:\src\Core\CrypticLauncher\patcher.c(97)
in errors file i see this at many different times
100113 02:06:06 1 MasterControlProgram[1]: OLE failed to initialize: 1
100113 02:06:06 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 1"
100113 04:14:27 1 MasterControlProgram[1]: OLE failed to initialize: 1
100113 04:14:27 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 1"
ok and i found the dxdiag but what do i post from it?
System Information
Time of this report: 1/12/2010, 20:07:31
Machine name: KREVIN-NINO
Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.090804-1435)
Language: English (Regional Setting: English)
System Manufacturer: BIOSTAR Group
System Model: TF720 A2+
BIOS: Default System BIOS
Processor: AMD Phenom(tm) 9950 Quad-Core Processor, MMX, 3DNow (4 CPUs), ~2.6GHz
Memory: 3328MB RAM
Page File: 928MB used, 4282MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.5512 32bit Unicode
DxDiag Notes
DirectX Files Tab: No problems found.
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Music Tab: No problems found.
Input Tab: No problems found.
Network Tab: No problems found.
DirectX Debug Levels
Direct3D: 0/4 (n/a)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
Display Devices
Card name: ATI Radeon HD 4600 Series
Manufacturer: ATI Technologies Inc.
Chip type: ATI Radeon Graphics Processor (0x9490)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_9490&SUBSYS_15901462&REV_00
Display Memory: 512.0 MB
Current Mode: 1280 x 1024 (32 bit) (60Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: ati2dvag.dll
Driver Version: 6.14.0010.7028 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 11/24/2009 18:26:52, 300032 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: ati2mtag.sys
Mini VDD Date: 11/24/2009 18:50:16, 4463104 bytes
Device Identifier: {D7B71EE2-D7D0-11CF-A66C-9A35A1C2CB35}
Vendor ID: 0x1002
Device ID: 0x9490
SubSys ID: 0x15901462
Revision ID: 0x0000
Revision ID: 0x0000
Video Accel: ModeMPEG2_C ModeMPEG2_D
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
DDraw Test Result: Not run
D3D7 Test Result: Not run
D3D8 Test Result: Not run
D3D9 Test Result: Not run
Sound Devices
Description: USB Audio Device
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: USB\Vid_0d8c&Pid_000c&Rev_0100&MI_00
Manufacturer ID: 65535
Product ID: 65535
Type: WDM
Driver Name: usbaudio.sys
Driver Version: 5.01.2600.5512 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 4/13/2008 09:45:12, 60032 bytes
Other Files:
Driver Provider: Microsoft
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 0, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run
Description: Realtek HD Audio output
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0662&SUBSYS_1565820F&REV_1001
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RtkHDAud.sys
Driver Version: 5.10.0000.5708 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 9/24/2008 16:32:18, 4818432 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 8000, 192000
Static/Strm HW Mix Bufs: 33, 32
Static/Strm HW 3D Bufs: 33, 32
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: Yes, Yes
I3DL2(tm) Listen/Src: Yes, Yes
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run
Sound Capture Devices
Description: USB Audio Device
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: usbaudio.sys
Driver Version: 5.01.2600.5512 (English)
Driver Attributes: Final Retail
Date and Size: 4/13/2008 09:45:12, 60032 bytes
Cap Flags: 0x41
Format Flags: 0x440
Description: Realtek HD Audio Input
Default Sound Capture: No
Default Voice Capture: No
Driver Name: RtkHDAud.sys
Driver Version: 5.10.0000.5708 (English)
Driver Attributes: Final Retail
Date and Size: 9/24/2008 16:32:18, 4818432 bytes
Cap Flags: 0x41
Format Flags: 0xFFF
DirectMusic
DLS Path: C:\WINDOWS\SYSTEM32\drivers\GM.DLS
DLS Version: 1.00.0016.0002
Acceleration: n/a
Ports: Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal, Default Port
USB Audio Device, Software (Kernel Mode), Output, DLS, Internal
Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
Registry: OK
Test Result: Not run
DirectInput Devices
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Keyboard
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x0D8C, 0x000C
FF Driver: n/a
Device Name: Ideazon Merc Stealth MM USB Human Interface Device
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x1038, 0x0510
FF Driver: n/a
Device Name: Ideazon Merc Stealth MM USB Human Interface Device
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x1038, 0x0510
FF Driver: n/a
Device Name: Gaming II
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0xFFC0, 0x001F
FF Driver: n/a
Device Name: Gaming II
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0xFFC0, 0x001F
FF Driver: n/a
Poll w/ Interrupt: No
Registry: OK
USB Devices
+ USB Root Hub
| Vendor/Product ID: 0x10DE, 0x077D
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 4/13/2008 09:45:37, 59520 bytes
| Driver: usbd.sys, 3/31/2003 03:00:00, 4736 bytes
For some reason the launcher is crashing whenever it tries to patch CO. And it also crashes when I try to patch STO.
You hardware looks to be ok. I not sure what the latest driver for the ATI is but I would try uninstalling the driver. reboot to safe mode use a driver removal type program (there is a couple out there and people have thier preferance) to remove any lingering driver files. then install the latest driver.
You can also see about downlaoding the latest DirectX End-User Runtime at http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3
I also seen post of people fixing ATI card problems with the game by using the catalyst control panel to reset to factory defaults
110122 00:30:24 1 Client[0]: Pixel shader (Shaders_Processed/D3d/Sprite_2d_Sm20_Unknown_Vendor.Phl) creation FAILED - D3DERR_INVALIDCALL
110122 00:30:57 2 Client[0]: Pixel shader (Shaders_Processed/D3d/Error_Sm20_S3g.Phl) creation FAILED - D3DERR_INVALIDCALL
110122 00:46:01 1 Client[0]: Pixel shader (Shaders_Processed/D3d/Sprite_2d_Sm20_Unknown_Vendor.Phl) creation FAILED - D3DERR_INVALIDCALL
110122 00:59:30 1 Client[0]: Pixel shader (Shaders_Processed/D3d/Sprite_2d_Sm20_Unknown_Vendor.Phl) creation FAILED - D3DERR_INVALIDCALL
you should start a new thread instead of necro one a year old. post a dxdiag report of your system but basicly it looks like your video card or driver is unable to support the game.
if you got the ccleaner: http://ccleaner.com.es/
Tried that to version what I downloaded from steam and CO own version and nothing.
Still gives the same error for me.
I'm running Win 7 Ult. 64bit
and hardware is under 1 year old.
I'm pretty sure that its not OS or hardware problem.
Interesting, some sort of Direct 3D error it seems. Doing my best to look into this, but not the easiest thing to pin down. I read something about another game where someone had to manually edit a config file (usually a text file in your game folder).
So perhaps you can try the following?
Only start the game in fullscreen, at a low resolution, only one active monitor, disable any crossfire or sli ....I can't gaurantee any of this, but could worth a try. I'll keep looking around the web for related errors.
Hello LoneWolf217,
From your statement above, you prove that the install is fine, however, you also prove that the "issue" is indeed related to the computer to which you're having issues with. In a nutshell, it's the computer, not the software we're dealing with.
That being said, This error is directly related to your C++ OLE Library. In essence, it's broke. You see, the computer uses .dll files as road signs if you will. When you double click on a shortcut on your desktop, like say Outlook so that you can access your email, the computer sends a request to the CPU to launch Outlook. In a perfect world, Outlook would launch and you'd be able to go about your business as usual. However, when you have a broken .dll file, 3 things can occur:
In this case, you're getting the error message as referenced by your following post:
Naturally, dxdiag and DirectX in general have nothing to do with this issue. This is all related to your C++ OLE Library.
How does this happen? Good question! Sadly, there's a multitude of different reasons why this might happen. One of the most common reasons is that your OS is corrupted. OS Corruption occurs when the user(s) doesn't regularly conduct computer maintenance, such as deleting temporary files and things like this.
How do I fix my OS? Another good question, however the answer isn't one that most folks like to hear, much less consider, which is of course; Reformat.
Now, I'm not the type of person to simply go, hey man, your stuff is broke, reformat, unfortunately this issue doesn't really allow for much elbow room if you will, thus the quickest and easiest method is to reformat.
My suggestion: If you can, backup your sensitive data to a removable harddrive and reformat. If you don't have anything worth saving, go ahead with the reformat. Reinstall XP and go from there.
If you'd like to learn more about the C++ OLE Runtime Library, please see these pages on Microsoft.com:
http://msdn.microsoft.com/en-us/library/aa243878%28v=VS.60%29.aspx
http://msdn.microsoft.com/en-us/library/ms974285.aspx
http://msdn.microsoft.com/en-us/library/aa232217%28v=VS.60%29.aspx
One more thing of note: Thanks to this post:
I can see that you do have some corruption going on here, unless of course you don't know how to set your clock in Windows. As you can see from the report above, your computer thinks that the date of process of this report was in fact 1/12/2010, 20:07:31 which we all know is not correct, unless of course you didn't do the report recently, which I doubt. That of course brings me back to OS corruption.
Another item of note is that your version of DirectX isn't up to snuff. You might want to update DirectX from Microsoft.com and attempt to launch once again, however, I really doubt that will fix your issue. I also took the liberty of bolding your Service Pack information from your quote above. I've never, ever advocated for any of my customers to update their XP beyond SP 2. There are many reasons why but the most important one is the simple fact that XP SP 2 is not only stable, but exceptionally robust. In laymans terms: SP 1 sucks, SP 3 sucks, SP 2 good. Sadly, the only way to "go back" to a previous Service Pack is not to uninstall it, but to reformat and not update past SP 2. I don't care what anyone says, sure you can "uninstall" SP 3, but it will not revert back to SP 2 without leaving a bunch of unwanted, craptacular files from SP 3 on there which of course interfere with the standard operations of the computer itself. This will of course lead to OS corruption.
I'm sorry to be the bearer of bad news my friend, however there's no real "nice" way to put this.
Best of luck and I really hope that my post has helped you out in one way or another.
This is April Fools Day not Easter, lets keep the miracles down or the neighbors might complain.
The Day they posted their original post!
You've been at this too long. Get back to the game and relax.
Woah, you're right about that! LOL
If you use DisplayFusion -- you will need to go through he steps int he link as this fixed it for me!
| ME | A "Guide" Book" | | I, have a "DREAM! | ( Member since Feb 2008 ) ... ?
[SIGPIC]http://i18.photobucket.com/albums/b132/AngelOfCaine/STILLS/Misc/CO-Sig_01e.png[/SIGPIC]
once i hit play, screen enlarges and goes black, then cryptic error comes up...
close with task manager, start again, it asks me if i want to verify ..
my wife sat next to me has no problems running it..
but like i say, before the patch it was fine.
This was my exact problem. I don't run Teamviewer but I do run Display Fusion. I uninstalled and reinstalled, no luck. Clicked and unclicked every possible combination of checkboxes in the Options of the launcher.
If you run Display Fusion you must do the following.
Right click the DisplayFusion icon in your system tray and pick settings.
Go to the Compatibility tab.
Click Add
Add both \Users\Public\Games\Cryptic Studios\CrypticError.exe
and \Users\Public\Games\Cryptic Studios\ChampionsOnline.exe
(adjust the path as necessary)
Uncheck all the all the boxes.
And OK your way out of it.
CO should run fine with DisplayFusion after that.
THANK YOU SO MUCH BLAKERS1984
thanks