That's good that the CVS compiles and runs on RPi.

The github version has quite a few more dependencies than before. New things like libpng, zlib, plus a couple of home baked things like xbrz scaling, fantasyname generator, music and sound, and possibly some other things I have failed to mention. It's not guaranteed that the additional libraries and bespoke stuff will work with the RPi compiler toolchain, or even if it compiles the application may not be compatible with either the chipset architecture or device drivers.

One cool thing to do would be to clone the git repository and progressively work backwards (or forwards) to find the last version of IVAN that compiles and runs on RPi. That should give an indication of what new features definitely break the game on RPi.

I'd be happy to put some money in the hat for this endeavor.

Sorry for putting you on the spot RustKnight, we understand
I think it would be more cost effective and easier on you to try for an online interview, either audio or video. Got to try with small steps first.

All that said, the first step would indeed be to approach original three. I'd say J_Kahvi would be easiest to contact. Just send him a PM to his account on this site, theoretically it should end up in his email inbox.

Have we still got money left over from the forum fundraiser?

I think this is a great initiative and I think your questions are good. I share Cap's sentiments about the chances of success however. Strangely I feel like you might be most successful with a face to face meeting. Go ask Ernomouse if he will let you use his place as a base of operations in Finland

I don't know how you would find the original devs, but their names are in the AUTHORS file: https://github.com/Attnam/ivan/blob/master/AUTHORS

You can find J_Kahvi (TV) here: https://github.com/MikkoTeippi and on the forum, he's into philosophy. I think hexi (HS) is in politics now, but there seems to be no sign of holybanana (TK). I think holybanana was last seen writing philosophy (imaginary phenomenology) with J_Kahvi in 2008/2009, but that was ten years ago... https://docplayer.fi/14464690-Eksakti-fenomenologia-tuukka-v...
Either J_Kahvi or hexi will be your best bet to help you track down holybanana.

For me (windows 8.1, 64-bit) doing alt-tab and also setting Frameskip to 1 seems to help restore things to similar performance as before this bug.

The alt-tab thingee is interesting. I think it must have something to do with IVAN partially losing its context. I'll try compile/testing at various points in the Git repo to see when this error might have crept in.

Awesome project!

It might have something to do with the ARM chipset being functionally different somewhere. Possibly need to modify the source code to make it fully compatible. Not an impossible task, but I personally wouldn't know where to begin.

What operating system are you running on your RPi? What compiler toolchain are you using to build for RPi?

Are you compiling the GitHub source? That has quite a few additional dependencies Try compiling IVAN CVS instead first to see if that works: https://attnam.com/projects/official/IVAN-CVS
IVAN CVS uses SDL1.2, so use the 'libsdl1.2-dev' library on e.g. Raspbian.

Let's try fix the first thing first. I actually remember seeing this error, but I don't remember how the hell I fixed it. The message about '>>' operators might be related to the size of int64 a la: https://support.microsoft.com/en-nz/help/168440/you-may-rece...
You need to tell Visual Studio the whole code needs to be handled as 32 bit.

Did you follow these steps?


It could be that step 2 helped me overcome the compile error after all. Here are my settings:

Under preprocessor definitions (Configuration->C/C++->Preprocessor) for Main, I have:

NDEBUG;USE_SDL;WIN32;_WINDOWS;VC;WIZARD;_WIN32;_USE_32BIT_TIME_T;%(PreprocessorDefinitions)

and for FeLib, I have:

NDEBUG;USE_SDL;WIN32;_WINDOWS;VC;_WIN32;_USE_32BIT_TIME_T;%(PreprocessorDefinitions)

Have a look in the attached pictures. Let me know if it helps or not

So the Windows "go slow" bug could be related to the numlock state eh? Thanks for the tip Izzy, I'll have to take a closer look at that when I get a chance.

While tooling around with the configs a bit more, I figured you can set relative paths in VS Express 2013 like this:

$(ProjectDir)SDL\lib\x86\SDL.lib
$(ProjectDir)SDL\lib\x86\SDLmain.lib

So no need for those absolute paths I mentioned earlier. I think VS 2017 will allow you to evaluate the expression in a window below so you can check the result is what you expect.

Hey RustKnight, you're in luck! I have been tooling around with Visual Studio Express 2013 for Windows Desktop (available here in m$ "hard-to-find" section): https://visualstudio.microsoft.com/vs/older-downloads/

I used the "Concurrent Version System" version of IVAN, purported to be the last version the original devs worked on, linked here: https://attnam.com/projects/official/IVAN-CVS
Download the source, which is ivan-cvs.tar.gz (you can unzip this using 7zip). I unzipped it somewhere with a handy folder name like C:\ivan-cvs

Then I downloaded SDL 1.2 (not SDL 2.x) from here: https://www.libsdl.org/download-1.2.php
I downloaded the SDL-devel-1.2.15-VC.zip for Visual C++. I unzipped this folder into C:\ivan-cvs and re-named it just "SDL" (so now I have a folder located here: C:\ivan-cvs\SDL

Next I opened the IVAN.dsw (found in C:\ivan-cvs) with Microsoft Visual Studio Click OK and it does the conversion step automatically, it will say it's no longer backward-compatible but you can ignore this.

IMPORTANT STEP: Once in Visual Studio, my very first step is to change the "Solution Configuration" in the drop-down menu to "Release"

Next I followed the incredibly well written SDL setup steps from https://thenumbat.github.io/cpp-course/sdl2/01/vsSetup.html
These steps are the same for SDL1.2 as they are for SDL2.0, except you should use SDL where they write SDL2 etc
Other changes were: I used absolute paths for the location of SDL, both the header files (where SDL.h is found) and the library files (where SDL.lib and SDLmain.lib are found)
IVAN is a little bit different in that the "Main" project (ivan.exe) is dependant on "FeLib" (a.k.a. the "Fatal Error" library - the original devs' custom C++ library). Simply follow the same configuration steps to both Main and FeLib. For instance, for FeLib, the Additional Dependencies can be found under "Configuration Properties- > Librarian -> General" and you can add

C:\IVAN-cvs\SDL\lib\x86\SDL.lib
C:\IVAN-cvs\SDL\lib\x86\SDLmain.lib

(This contrasts with Main, where this is done under "Configuration Properties- > Linker -> Input", as per the instructions in the SDL setup guide I linked).

You can press F7 now to build, but you will get errors. I made them go away by doing the following:

1. Added _USE_32BIT_TIME_T to "Preprocessor Definitions" which I found under Alt-F7 "Configuration properties -> C/C++ -> Preprocessor"
2. Added WIN32 and _WIN32 to Preprocessor Definitions (this seemed not ti fix anything, but I did this for superstition)
3. Replaced #include "afxres.h" with #include "windows.h" in Ivan.rc (seemed to overcome the "afxres.h not found" error, thanks to this answer here: https://stackoverflow.com/questions/3566018/cannot-open-incl...)
4. I used absolute paths for SDL.lib and SDLmain.lib, like so:

C:\IVAN-cvs\SDL\lib\x86\SDL.lib
C:\IVAN-cvs\SDL\lib\x86\SDLmain.lib

Then I pressed F7 to compile and build. It magically builds IVAN.exe located at C:\IVAN-cvs. If you click on it to run, you will get another error saying SDL.dll not found. Copy SDL.dll from C:\IVAN-cvs\SDL\lib\x86 to the folder where IVAN.exe is and then open IVAN again. It will run the game.

Please let me know if you get stuck and I will see what I can do to help. If you're unsure about my VS configs, I can post screenshots if you like

Corollary: I wonder if Appveyor does Visual Studio builds in the cloud??