Forums

No. Basically, you need "plugins/platforms/' in the root of Drakensang's folder, or in the root of the QT5 folder, with the 'qwindows.dll' in that folder. You will need to grab the 32-bit version of the plugin 'platforms/', which contains that .dll from a MSVCR2012 or MSVCP2012 install (I cannot remember which one off of the top of my head), and put that 'platforms' folder (which is actually a plugin module) in the 'plugins/' directory in the GT5 folder (there should be a plugins directory) first, and if that fails, then try copying the whole 'plugins/' folder to Drakensang's root folder. It should be able to find itself with no issues. Also, make sure that in Drakensang's root folder, you add libEGL.dll or libEGLd.dll and those other ones you listed, as well. You will need those. It should be something like:

|-drakensang

    |--thinclient.exe

    |--libegl.dll

    |--libegld.dll

    |--those other dll's

    |---plugins/

        |---platforms/

            |---qwindows.dll

NOTE: I have seen some people say that if plugins (like 'platforms/') are in the app root, and not the QT root, then you do not need the 'plugins/' folder, so if the above does not work, attempt this:

|-drakensang

    |--thinclient.exe

    |--libegl.dll

    |--libegld.dll

    |--those other dll's

    |---platforms/

        |---qwindows.dll

 

QT5 changed it's project structure when moving to VC2012, and I guess in Wine it doesn't know where to find it. I got it working by working it in the Drakensang root folder root folder, as stated above, with Wine 1.7.28 (which has the fix for the FindFileFirst) issue. Hope this helps. Let me know if you are still running into issues. 

BTW: with VC2012, apparently appending things to PATH is a no-no, as it is supposed to be able to find it's stuff relative to where it is at, and I think that is why it is screwing up; it is looking for vc2012, but it is looking to find a relative path, which of course, you don't have, because of the special folder structure and the 'platforms/' module/plugin not being present in the QT root or in the app root. 

Edité par RoninDusette

its strange because the Drakensang root folder already has a platforms folder with qwindows.dll

I'll try creating a plugins/platforms folder and put it in there

I was just going to post up and say that vc2012 is not needed. As per their site:

http://qt-project.org/doc/qt-5/windows-deployment.html

It only needs 2010, so make sure that msvc2010 and msvcr2010 (specifically, msvcp100.dll and msvcr100.dll, respectively) are in your virtual drive,

If that does not work, then try see if moving the 'platforms/' folder to the QT root in 'plugins/'. The path is hardcoded into QT, so it has to pick it up in one of those places, either the app root or the QT root. Apparently libEGL.dll and libGLESv2.dll, and possibly other are required in one of those places, as well. 

At that site, they show this:

Qt5Core.dll

Qt5Gui.dll

Qt5Widgets.dll

Those should all be present at the same level as the 'platforms/' folder in the app root, as well as the libegl and all of that. I used 2012 runtime, but since we can install 2010, and that is what it requres, that would be a better option. 

I am actually going to delete my virtual drive again here in a bit and test it, just to make sure that I can reproduce success. 

I am seriously going to start writing some Wine patches eventually. lol. Gotta learn C first. 

moving it to platforms/ folder in the QT root is in Linux or my virtual drive?

I don't have QT installed yet, but should I install it with PlayOnLinux in my virtual drive to create that path?
I hope this will eventually be updated in Wine as well because I'm sure there are a lot of interfaces using Qt and will be upgrading

No, the QT5 install folder in the virtual drive. You shouldn't need anything outside of the virtual drive.

This isn't actually a Wine issue; it is simply lost. So, either the Drakensang root, or after you install QT into the virtual drive (I am almost positive that the installer does this for you), in the QT root folder, in the plugins/ folder. 

Make sure that msvcr2010 and msvcp2010 are installed in the virtual drive, as are those gles and egl libs. If all of that fails, you could also use dependency walker on that virtual drive to tell you what is missing, but I don't know what else could be missing. lol. 

I think I get what you are saying.

When I install Drakensang it shows QT files during the installation.  So I hope that is what you mean by installing QT (previously you linked to a QT installation with apt-get)

I don't remember seeing packages in PlayOnLinux for mscvr2010 and msvcp2010

I've seen vcrun2010 and have used it in the past.  I'll search for all the libraries you are recommending when I test tonight.

This really sucks because Drakensang was never complicated, it was the quickest and simplest installation EVER (hands down)!

Thanks for your help again!

I am probably making it more complicated. lol. vcrun2010 is fine. I am stupid. I am retesting it tonight. I know I mentioned the QT libs in Linux, because Wine does a lot of redirecting to native linux stuff, but this looks to be broken again for me now, after deleting my virtual drive. I will know more here in a bit. 

Ok, I'm at work on Windows right now, but I do have my Chromebook with Ubuntu 12.04 on it. Unfortunately I'm stuck with Intel HD 2000 video chip which won't run Drakensang 

By the way, Drakensang installed LibEGL.dll in the games root but not the LibEGLd.dll

So when it did work, you were using the qwindows.dll from Drakensang in Windows?

No. I replaced it with the SDK one. Though, I think there is a difference. libEGLd.dll I just downloaded from der webz. I am actually working in it right now. I will let you know in a bit what I find. I am trying to figure out what exactly I did yesterday that worked that is different today. 

When I select Windows XP, the QT error goes away, but the game refuses to update.  Here is my log:

[11/13/14 12:06:51] - Running wine-1.7.28 thinclient.exe (Working directory : /home/booman/.PlayOnLinux/wineprefix/drakensang/drive_c/Program Files/Drakensang Online)
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory[11/13/14 12:07:23] - Running wine-1.7.28 winecfg (Working directory : /usr/share/playonlinux/python)
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory[11/13/14 12:10:22] - Running wine-1.7.28 thinclient.exe (Working directory : /home/booman/.PlayOnLinux/wineprefix/drakensang/drive_c/Program Files/Drakensang Online)
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directoryfixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:system:SetProcessDPIAware stub!
fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046}
fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
fixme:toolhelp:Heap32ListFirst : stub
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
fixme:ntdll:NtLockFile I/O completion on lock not implemented yet

With Wine 1.7.28-FindFileFirst (or whatever it is called) lets me run it in Windows 7 mode with no QT error. I cannot update, though I am running relay on the debugger and waiting for the output. 

So, what I am going to do is patch Wine 1.6.2 (which is what you had working in your guide) with the following patches, and see if that works. That fixes the QT problem, and it obviously worked with that version of Wine. I will get to that in the next day or so and let you know. 

 

https://github.com/PlayOnLinux/wine-patches/tree/master/custom/FindFirstFile

Were you able to sign in and get to the character screen?

I can PM my credentials if you want

I signed up for it. I was able to sign in and everything. No problem. That was last night, though. I don't know what I did, but I had it working last night. Either way, I am compiling a new patched Wine 1.6.2 to get around this issue. Hopefully those patches work on that version. From the looks of them there should be no problem. I looked up and down, and I cannot find any other reason for the crash. If it worked for 1.6.2, and the only thing that changed is QT, then this patch should fix the QT error and restore functionality like usual. 

Awesome, let me know when its done and I'll test.  If it works then I will post that its fixed with your patched version of Wine.

If it works I am going to write a script. I don't see why this would not work. It is actually compiling as we speak. Those patches were made for newer wine versions, so I had patch manually, line-by-line. I don't know too much about C, so we will "C" how it goes. haha. 

So, yeah. I don't know what to tell you. The furthest that I can get is with 1.7.28-FindFirstFile (or whatever it is) 32-bit, set to Windows 7, and no extra stuff installed. That fixes the QT5 problem. Now I cannot get it to finish the download, as it always spits out an error about the connection being dropped. I have tried like, every damn debug flag, and I cannot see where it is causing it to error out. It is hard to find, because it is not throwing an ERR or a backtrace. 

The difference between 1.6.2 and .1.7.28 and those patches is so great, that even manually applying them, it still failed on compilation. 

If any of the more experienced people here want to chime in, feel free. I am at a loss. 

I get the same exact error even with Windows XP.  Thanks for helping out with this.  Sooner or later someone will figure out what is going on with Drakensang.

I'll keep researching and if I find a solution, I'll definitely post it here.

I was just going to say that. hahaha. Late last night I just decided to try it in Windows, and it is broken natively on there, too. I feel SO dumb for not checking that first. haha. They need to fix it in Windows first. hahaha.