OTClient doesn't start

[tarantonio]

I'm in trouble with the latest builds of otland/otclient, it doesn't start in my windows 10 machines.
I tried the .zip with all the dlls required, tried to compile myself and it doesn't start and no errors or wathever.
I have no problem with old otclient builds, like the ones posted here on otland builds thread
Anyone with the same problem?

 

[jackl90]

I have the same problem, using visual 15, on windows 10 64 bits, my otclient no open and no errors... i just got some warnings after compile.

 

[tarantonio]

I have the same problem, using visual 15, on windows 10 64 bits, my otclient no open and no errors... i just got some warnings after compile.

I have also that problem with the appveyor automated builds from otland/otclient...

 

[jackl90]

My first time compiling last otclient, i got a error AL/h in sound/declarations source.
Changed <al/al.h> and <al/alc.h>
After this fix, my otclient no open after compile, idk why

 

[tarantonio]

My first time compiling last otclient, i got a error AL/h in sound/declarations source.
Changed <al/al.h> and <al/alc.h>
After this fix, my otclient no open after compile, idk why

I'm not talking only about self compiled ones, I talk about some builds like automated builds from otland/otclient
On other computers I can open the same otclient, but not in mine, I was asking to know what can be the problem to no open with no errors

 

[Don Daniello]

There's an issue that we're trying to solve. The problem is physfs.dll. The OTClient compiled by AppVeyor doesn't start but if I copy the physfs.dll compiled locally into the OTClient downloaded from AppVeyor, it works.

I don't know why yet.

 

[tarantonio]

There's an issue that we're trying to solve. The problem is physfs.dll. The OTClient compiled by AppVeyor doesn't start but if I copy the physfs.dll compiled locally into the OTClient downloaded from AppVeyor, it works.

I don't know why yet.

Curiously, the same appveyor downloaded otclient starts normally on my laptop ¿?

 

[Don Daniello]

Curiously, the same appveyor downloaded otclient starts normally on my laptop ¿?

What's your Windows version and build?

 

[tarantonio]

What's your Windows version and build?

That's the PC where it doesn't start

 

[tarantonio]

There's an issue that we're trying to solve. The problem is physfs.dll. The OTClient compiled by AppVeyor doesn't start but if I copy the physfs.dll compiled locally into the OTClient downloaded from AppVeyor, it works.

I don't know why yet.

I compiled the client on that PC (VS 2017 and vcpkg method) and doesn't start, also I copied the local compiled dll on the appveyor downloaded one and still doesn't start.
Maybe it can be a problem from my Windows build, but I still haven't found the source for the problem.
Some old otclients start without problems also on that PC (the one from otland forum builds for example)

 

[tarantonio]

What's your Windows version and build?

On this PC all is OK, the compiled client is working, last appveyor one is working too.

 

[xKrazyx]

I bring the issue up in the OTC github, instead of trying to help, my issue is instantly closed by Ironyt.. xD

Seems like Ironyt closes a lot of issues for some reason, whereas half of those issues are already fixed on his server? (hmm)

From what i've read some ppl who make the switch from visual studio to codeblocks solves the issue.

I have this issue as well compiling in vs, its on about 10%-15% of machine s/ (Older machines 32 bit on any windows version ive seen this bug on both windows 7 and 10(not 64 bit if that helps))

Stacktrace isnt very helpful and the program fails to start on any compatibility mode. Tried different build versions, 2015, 2017...
At first thought it was an antivirus trigger but its not. Weird bug :/.

I havent tried compiling on a different machine yet.

hard to debug because dont have continuous access to a bugged machine trying to open the client :/

Will post more if I find anything.

 

[tarantonio]

It seems some devs have solved this issue or dont have it when they compile, however when I bring the issue up in the OTC github, instead of trying to help, my issue is instantly closed by Ironyt.. xD

Seems like Ironyt closes a lot of issues for some reason, whereas half of those issues are already fixed on his server? (hmm)

From what i've read some ppl who make the switch from visual studio to codeblocks solves the issue.

I have this issue as well compiling in vs, its on about 10%-15% of machine s/ (Older machines 32 bit on any windows version ive seen this bug on both windows 7 and 10(not 64 bit if that helps))

Stacktrace isnt very helpful and the program fails to start on any compatibility mode. Tried different build versions, 2015, 2017...
At first thought it was an antivirus trigger but its not. Weird bug :/.

I havent tried compiling on a different machine yet.

hard to debug because dont have continuous access to a bugged machine trying to open the client :/

Will post more if I find anything.

Codeblocks have the same problem for me.
Iryont closed my issue too.
On otland/otclient it's open, let's see if they can help us.

 

[BahamutxD]

Codeblocks have the same problem for me.
Iryont closed my issue too.
On otland/otclient it's open, let's see if they can help us.

This is the exe you requested me on Github MEGA (https://mega.nz/#!ORoxFCqI!PVLNFPDTdY3YNib7zrS5rHIbq_TTF_aTBiJh75Zsol0)

Got compiled on VS17. Never mind the icon, too lazy to fix it.

It runs fine for me on.

 

[Steve Albert]

It seems some devs have solved this issue or dont have it when they compile, however when I bring the issue up in the OTC github, instead of trying to help, my issue is instantly closed by Ironyt.. xD

Seems like Ironyt closes a lot of issues for some reason, whereas half of those issues are already fixed on his server? (hmm)

From what i've read some ppl who make the switch from visual studio to codeblocks solves the issue.

I have this issue as well compiling in vs, its on about 10%-15% of machine s/ (Older machines 32 bit on any windows version ive seen this bug on both windows 7 and 10(not 64 bit if that helps))

Stacktrace isnt very helpful and the program fails to start on any compatibility mode. Tried different build versions, 2015, 2017...
At first thought it was an antivirus trigger but its not. Weird bug :/.

I havent tried compiling on a different machine yet.

hard to debug because dont have continuous access to a bugged machine trying to open the client :/

Will post more if I find anything.

Here is an idea use working sources and compile those. Once you have a working source then update the working sources to the latest sources by hand. All you need is a differential tool such as meld which runs on both windows & linux. This method of updating can take a lot of time but it will help you find bugs within the code that you can either fix yourself or address whomever is maintaining the project,

Just posting compile errors doesn't mean people are going to be able to help you. Now posting actual code will make it easier for others to assess the problem and find a solution.

 

[jackl90]

This is the exe you requested me on Github MEGA (https://mega.nz/#!ORoxFCqI!PVLNFPDTdY3YNib7zrS5rHIbq_TTF_aTBiJh75Zsol0)

Got compiled on VS17. Never mind the icon, too lazy to fix it.

It runs fine for me on.

View attachment 35141

What modifications have in this exe?

 

[tarantonio]

This is the exe you requested me on Github MEGA (https://mega.nz/#!ORoxFCqI!PVLNFPDTdY3YNib7zrS5rHIbq_TTF_aTBiJh75Zsol0)

Got compiled on VS17. Never mind the icon, too lazy to fix it.

It runs fine for me on.

View attachment 35141

it doesn't start on mine, same windows version and build...
It's very dissapointing.

 

[BahamutxD]

What modifications have in this exe?

Ninjalulz attemp to fix idle animations and

AWARE_UNDEGROUND_FLOOR_RANGE = 4,

Shouldn't matter for this issue.

it doesn't start on mine, same windows version and build...
It's very dissapointing.

There must be something wrong on your end OS related. I can confirm that .exe works just fine on 5 different machines (most of them this OS version too)

 

[tarantonio]

Ninjalulz attemp to fix idle animations and

AWARE_UNDEGROUND_FLOOR_RANGE = 4,

Shouldn't matter for this issue.



There must be something wrong on your end OS related. I can confirm that .exe works just fine on 5 different machines (most of them this OS version too)

I also tried the same files on a brand new installation of windows on another computer today, same version and build, and I have the same problem.
And older builds of otclient or some recent downloaded clients from private servers are working... (for example last build of otclient downloaded from this forum is working)

 

[xKrazyx]

I also tried the same files on a brand new installation of windows on another computer today, same version and build, and I have the same problem.
And older builds of otclient or some recent downloaded clients from private servers are working...

is your OS 64 or 32? Those who cant open my client only have 32 so far.. I made sure they have service packs too so no issue there.

They can open medivia client but no other otclient. cant open any other otclient apparently like the problem you are having.