Failing maps

[Temtaime]

Just noticed that prt_cas looks like this

Are there other bugged maps in the viewer ? Or maybe this one is mine grf problem ?

[ReckedCat]

Seems to render fine for me, see attached. Unless you're referring to a map other than prt_cas? Using release build 0.4.0. 

 

Edit: Oops, hadn't realized I had an old build. Tried again with build #18, and it still rendered fine. 

Edited May 8, 2018 by ReckedCat

[ReckedCat]

Compiling from the latest source (as debug, I can't get release to compile, almost certainly a msvc issue on my end) seems to be fine as well.

[Temtaime]

Thanks !

Btw what are the errors about msvc ? Maybe i can help with them.

Also - use ldc2 to compile release build.

Can you extract and upload somewhere your ptr_cas.rsw/.gnd ?

[ReckedCat]

prt_cas.7z

See attached.

 

Regarding my builds failing, I tried using the dlang.org compiler, but it couldn't seem to find the MSVC libraries, so it would never link the application.
I had similar issues trying to use the dmd that you linked to/provided from the repo's README.

I "resolved" this by, installing the dlang package to C:\D\, unzipping the dmd and ldc to that directory, (C:\D\dmd and C:\D\ldc), using the sc.ini and ldc2.conf as reference, just copied files from the MSVC installation path (C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.13.26128\lib) into a directory relative to dmd & ldc (C:\D\msvc) [note: I couldn't seem to make Sublime Text happy during compile by editing my system path to include the MSVC lib directory, or editing the sc.ini file, not sure why, which is why I resorted to just moving the files].
I also grabbed the ucrt libs (C:\Program Files (x86)\Windows Kits\10\Lib\10.0.16299.0\ucrt) and copied them to the C:\D\msvc directory as well.

I'm able to compile the debug version fine, but when it runs the ldc2 compile, it fails with:

Performing "release" build using ldc2 for x86_64.
derelict-util 3.0.0-beta.2: building configuration "library"...
Microsoft (R) Library Manager Version 14.13.26132.0
Copyright (C) Microsoft Corporation.  All rights reserved.

LINK : fatal error LNK1171: unable to load mspdbcore.dll (error code: 193)
Error: C:\D\msvc\bin\lib.exe failed with status: 1171
ldc2 failed with exit code 1.

Noting that the referenced library should come from the MSVS Common7/IDE (C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\Common7\IDE), I tried adding that directory to my path (confirming that yes, the .dll exists in that directory), which didn't seem to change anything. I then resorted to copying that into the C:\D\msvc\bin\ and C:\D\msvc\x64\bin, and saw no change.

I'm admittedly 0% familiar with using MS's libraries or toolchains (I've only worked in C/C++ GNU and Borland really), so I recognize I'm probably making a terrible mess.

[ReckedCat]

I tried reinstalling the dlang version of dmd, and redownloaded LDC 1.9.0 from https://github.com/ldc-developers/ldc/releases, and got further. Now I'm just running into unresolved sqlite3 symbols.

WARNING: A deprecated branch based version specification is used for the dependency pegged. Please use numbered versions instead. Also note that you can still use the dub.selections.json file to override a certain dependency to use a branch instead.
Performing "release" build using ldc2 for x86_64.
derelict-util 3.0.0-beta.2: target for configuration "library" is up to date.
derelict-sdl2 3.1.0-alpha.3: target for configuration "derelict-sdl2-static" is up to date.
pegged ~master: target for configuration "default" is up to date.
stb 1.3.0: target for configuration "library" is up to date.
consoled 1.0.3: target for configuration "library" is up to date.
tt-utils 1.3.6: target for configuration "library" is up to date.
perfontain:engine ~master: building configuration "library"...
perfontain:ro ~master: building configuration "library"...
perfontain ~master: building configuration "application"...
   Creating library .dub\build\application-release-windows-x86_64-ldc_2079-0EDC65C5909D81BCF3531AB3663F1401\perfontain.lib and object .dub\build\application-release-windows-x86_64-ldc_2079-0EDC65C5909D81BCF3531AB3663F1401\perfontain.exp
perfontain.obj : error LNK2019: unresolved external symbol sqlite3_exec referenced in function _D2ro2db4RoDb__T5queryTAyaZQlMFQiZAS3std8typecons__T5TupleTQBkZQl
perfontain_ro.lib(ro.db.obj) : error LNK2001: unresolved external symbol sqlite3_exec
perfontain_ro.lib(ro.db.obj) : error LNK2019: unresolved external symbol sqlite3_open referenced in function _D2ro2db4RoDb6__ctorMFZCQwQvQu
perfontain_ro.lib(ro.db.obj) : error LNK2019: unresolved external symbol sqlite3_errmsg referenced in function _D2ro2db4RoDb6__ctorMFZCQwQvQu
perfontain_ro.lib(ro.db.obj) : error LNK2019: unresolved external symbol sqlite3_close referenced in function _D2ro2db4RoDb6__dtorMFZv
.dub\build\application-release-windows-x86_64-ldc_2079-0EDC65C5909D81BCF3531AB3663F1401\perfontain.exe : fatal error LNK1120: 4 unresolved externals
Error: C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.13.26128\bin\HostX64\x64\link.exe failed with status: 1120
ldc2 failed with exit code 1.

 

[ReckedCat]

I was able to "resolve" the link errors by grabbing a copy of the sqlite3.dll precompiled for windows x64 and generating a .lib using MSVS's lib.exe

lib /def:sqlite3.def /out:sqlite3.lib

then modifying the package.json "libs" line to include "sqlite3", and recompiling.

Note, threw sqlite3.lib in utils/deps (with the rest of the referenced libs, configured by lflags-windows), and the .dll in bin (required since it isn't statically linked)

With that, I was able to compile and run, but I get the feeling I'm going way off-base.

[Temtaime]

I have not installed msvc on my desktop because it's too large and installs too many unused items for me.

I'll publish a tool that creates from msvc its portable version compatible with dmd/ldc builds published by me. Don't know when, but i'll do my best.

Yeah, they come with static sqlite library.

[Temtaime]

Hmm, just tried mine ptr_cas with newer build and it works

Seems i broke something when was testing new features