Dirtsand Early 2018

[Deledrius]

Until now I have been running the Dirtsand Client

There is no "Dirtsand Client". Which client did you mean?

[J'Kla]

I did mention it in the post plClient.exe.

To get dirtsand to link as per Destiny create a shortcut of plClient.exe (you can rename the shortcut) and under Proporties edit the Target details, add a space followed by -LocalData

As I say this works fine on a Windows 7 PC.

[Christian Walther]

That sounds suspiciously like the crash we used to get on MOULa when the Cyan support server was down so it couldn’t get the status message. Especially the “about half a minute” bit, since the status message is refreshed every 30 seconds, IIRC. But I don’t think that crash applied to the H-uru client. So yes, it would be useful to know what client you are using. “plClient.exe” is not a useful answer, as all source bases compile to a binary of that name. What Deledrius meant was, where did you download it, or what sources was it built from? Do you see the server status message in the login window?

[J'Kla]

This is the link to the original download http://files.mystler.eu/Client.zip this is Destiny compiled client.

This is the client file I have been using for all of my Windows7 links for my LAN shard and the Destiny shard only with changes to the dirtsand.ini file to differentiate them.

This still works perfectly for my Windows 7 PC's both over the LAN and using a no-ip link to gain remote access.


[edit]
As for the detail of the message pop up window telling me Microsoft will be looking into it (as if that's going to happen) I was at at a remote site doing stuff with "The Great Exhibition of the North" I am in the process of replicating the setup here and I will be back there on Friday where I can take screen shots etc.
[/edit]

[J'Kla]

Update

New testing strategy

I built a new laptop usung Windows7 Pro

I copied my installed working client folder complete from another Windows7 Pro that has a working connection to the Shard.


On this laptop I created a new desktop shortcut to plClient and set the target to have the -LocalData extension.

And this has the same falling over.

So its not Windows 10

Screen shot of error attached.

plClient Error.png (11.26 KiB) Viewed 29953 times

Install of MOULa works fine.

[edit]
I have found a undocumented feature with the Windows7 Pro I was using.

A troubleshooter corrected a windows Update of 129 updates now in progress I will report bak once this is sorted. Sometimes I hate Windows.

Is there any probability of a dirtsand client for Linux one thats native and not something that uses Wine. Just a question I am well prepared for a negative.
[/edit]

[Deledrius]

Is there any probability of a dirtsand client for Linux one thats native and not something that uses Wine. Just a question I am well prepared for a negative.

Paradox has been working on porting the engine's graphics from DirectX to OpenGL, but it's a huge task and not yet complete. That and converting the physics engine to something non-Windows-only are the major things standing in the way of a native Linux and OSX game.

[J'Kla]

I had a feeling it was going to be too big of an ask.

[Deledrius]

Yeah, it's one of those things nearly everyone wants, but we just don't have the coding power to make it happen on a non-geologic timescale.

[J'Kla]

I would call it not quite geolgical but definately Cyan time scale.

[J'Kla]

I have built a laptop Windows 7 Pro 4 Gig memory that runs MOUL ok

When I try this laptop with dirtsand plClient crashes with the following detail.

Code: Select all

Problem Event Name:	APPCRASH
  Application Name:	plClient.exe
  Application Version:	0.0.0.0
  Application Timestamp:	58a2fa7f
  Fault Module Name:	plClient.exe
  Fault Module Version:	0.0.0.0
  Fault Module Timestamp:	58a2fa7f
  Exception Code:	c0000005
  Exception Offset:	004fbe8f
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	2057
  Additional Information 1:	0a9e
  Additional Information 2:	0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:	0a9e
  Additional Information 4:	0a9e372d3b4ad19135b953a78882e789

I think I may have figured the Windows 10 issue I believe plClient may be trying to use an older version of DrectX and the DirectX Windows 10 installation adds MSVCR120_clr0400.dll and does not install MSVCR120.dll

That does not answer this issue as a Windows7 installation Of DriectX does add MSVCR120.dll