Client Crash after black screen at startup

[dstokes]

The Client crashes seconds after startup. It displays a black screen and then dies. I have .net 1.1 installed with directx 9 and the managed DX package. Runing dxdiag produces no errors in DX9. The debug.log from the client is as follows.
[code:1]Entered Main()
Environment..
Operating System = 'Microsoft Windows NT 5.1.2600.0'
.NET Framework = '1.1.4322.573'
Base Directory = 'D:\Krrios' Client\Beta 9 Release 1'
Data Directory = 'D:\Ultima Online'
Done
Setting up interop communications...done
Initializing Strings...done
Benchmarks: low resolution
Main()..
Initializing Display...done
Initializing DirectX..
Unhandled exception
Object -> Name: Client.exe
There are no context policies.

Error Code -> -2146232832
Error String -> Unknown
Type -> Microsoft.DirectX.Direct3D.InvalidCallException
Message -> Error in the application.
Source -> Microsoft.DirectX.Direct3D
Target -> Void .ctor(Int32, Microsoft.DirectX.Direct3D.DeviceType, System.Windows.Forms.Control, Microsoft.DirectX.Direct3D.CreateFlags, Microsoft.DirectX.Direct3D.PresentParameters)
Inner ->
Stack ->
at Microsoft.DirectX.Direct3D.Device..ctor(Int32 adapter, DeviceType deviceType, Control renderWindow, CreateFlags behaviorFlags, PresentParameters presentationParameters)
at Client.Engine.InitDX()
at Client.Engine.Main(String[] Args)[/code:1]

[Mr_Rappa]

I'm not sure of the debugging.... but the description matches exactly what I get.

Fresh install, no config change, go to run it and it shows a big black screen and crashes.

Pity, as my brother's now achieving much better connection results using your client krrios, and i was keen to give him a run for his money!

**edit note**
forgot to mention that I'm running .NET framework 1.1, directx 9.0b, and also have the managed dx package installed.

[ausplaya]

have you tried reinstalling directX 9b? only thing I can think of soz

[tejster24]

It's a DirectX problem. Have fun.

[Mr_Rappa]

I've reinstalled DirectX9.0b and then the managed libraries.... still no joy.

I guess this client isnt going to work for me.

[ausplaya]

If that's the case, and I'm no expert with ddirectX, but, maybe reinstalling don't do much, like reinstalling windows, it doesn't overwrite the dmg'd or corrupt files? I dunno, but hell I'd reformat if it meant this client worked coz it rocks

[psz]

Reinstalling Windows or DirectX or Drivers or .Net or anything else DOES overwrite files/settings... That's the whole point to RE-Installing.

[ausplaya]

well you have your opinion, I have mine. I know my background, but don't know yours so I wont be jumping to any conclusions, however I know I can back up what I said very easily. either way it's strange that it doesn't work for you Mr_Rappa, only other thing I can think of is possibly a conflict somewhere. Have you gone into device manager, clicked on "view" menu, selected "show hidden devices" and seen if there are any devices at all in conflict?

[Mr_Rappa]

No conflicts here

[psz]

I know my background too ;->

I know what I did less than a week ago.

I know what I had to do over 500 times per year for five years for work.

If it didn't overwrite files, you wouldn't have to re-apply Windows Updates ;->

When you reinstall, say, Madden 2004, it removes the files, then re-writes them. (This is the case for 99% of all games written since about 1996 or 1997). On most newer games (and apps) it will keep any saved files (lately in the My Documents directory. Bout damn time they started using it :-P)

When you reinstall (most) drivers, they overwrite the files in the System/System32 directory (Which is why on Win9x you had to restart the machine anytime you reinstalled the same driver: It overwrote files in the System/System32 directory, and system saw "changed file", freaked, and would insist that the changes would not take affect until restart... Even though they SHOULD have been the same files). WinNT isn't AS annoying as 9x in that regard, though TV Tuner software still tends to require a restart once new drivers are installed.


Now, for DirectX it's more difficult, as the default installer of any version past 2 will NOT reinstall if the existing version is current or older... (DirectX 2 had a nasty habit of outright overwriting ANY version of DirectX... 2, 3, 5, 6, 7, 8, 9, didin't matter).

In THAT case, you tend to have to use a 3rd party program, UNLESS there are corrupt/missing files... Those the default installer WILL replace.

[Mr_Rappa]

I dont know if this makes any difference, but I installed DirectX 9.0b using the web installer.

My brother used the redistributable DirectX 9.0b and has no probs.

I'm going to give it a shot hopefully when I get home and let you all know if this works.

[psz]

It *SHOULDN'T* make a difference, but I personally always use the redist... Mainly so that if I need to install on another machine (Or reinstall on whatever machine I'm on), I don't have to bother DLing again.

(Considering I've reinstalled Windows on THIS machine once in the last two years, the latter is not generally a problem ;->)

[Mr_Rappa]

OK - I can now use Krrios Client!

What did I change?

My video card. I was using an SiS video card till recently and couldnt for the life of me get Krrios Client working. Now I have an nvidia geforce4 installed and krrios client is working perfectly.

[psz]

Reason: SiS onboards (and some of their non-onboards) don't support all of the DirectX features (Hardware TnL, for example)

[x33905]

Is anyone else in my boat here?

Reinstalled directx 9b multiple times.

.Net framework 1.1 installed.

Managed DX installed. (I think - although when I run the mdxredist.msi a progress bar fills then tells me that a network error is occuring when it tries to read the file. Something about a network resource being unavailable)

Compatible graphics card. (GeForce 4)


Client still crashes at blackscreen :?

[drkbg]

can anyone tell me which video cards work with Krrios' Client?

[ausplaya]

nvidia seems to work very well with everyone I know

[drkbg]

i have vanta and it does not work
the same problem with black window and crash...