This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: 1
1
General ENIGMA / Vector graphics? Bones on sprites?
« on: December 18, 2019, 06:05:49 pm »
I did a quick forum search and the most relevant answer I found was a topic from 2014. So, I'd like someone who knows better about the engine to kindly answer me:
Why I'm asking: the project I have in mind is basically the player controlling a robot, running around gathering new pieces like arms, legs and torsos, which are visually different. Zooming in and out to show the same image rather than having a separate set of images for close ups would be much better for me
- Is it possible to use vector graphics, somewhat similar to Flash?
- Is it possible to add bones, joints or something similar to sprites?
- Is it possible to change the origin of a sprite sheet to a particular frame while the game is running? (I'm almost certain the answer to this one is yes, but I'd like confirmation)
- Is it possible to change a palette color? Say, my sprite is saved with a 16 color palette, after it is loaded, can I change the color value of one of those 16 colors?
Why I'm asking: the project I have in mind is basically the player controlling a robot, running around gathering new pieces like arms, legs and torsos, which are visually different. Zooming in and out to show the same image rather than having a separate set of images for close ups would be much better for me
2
General ENIGMA / Re: ENIGMA - Easy installation
« on: April 15, 2019, 08:41:45 pm »Here's updated version of scripts! v2 [BETA]
Changelog:
- re-writed with MUCH MORE relative structure, which provide some new functions:
- Cross-platform update. (Windows - 100% worked, Linux - not tested, Mac - not available now). Working on it.
- Freedom! Now you able to define your parameters for install/ launch. MAKE SURE THAT YOU MADE BACKUP OF VARS.INI BEFORE EDIT!
For Windows, script (as always) should be extracted from 7z and dropped to msys root folder (in order to get .bat files work).
It still needs test. If you will find some bugs - drop info here and I'll fix that.
I'm testing this, this is the very first problem I got with the .bat files:
Code: [Select]
C:\msys64\ENIGMA\windows\install-or-update\mingw64>mingw64-install-pro.bat
C:\msys64\ENIGMA\windows\install-or-update\mingw64>cd ..
C:\msys64\ENIGMA\windows\install-or-update>rem \ENIGMA\scripts\windows\mingw64\
C:\msys64\ENIGMA\windows\install-or-update>cd ..
C:\msys64\ENIGMA\windows>rem \ENIGMA\scripts\windows\
C:\msys64\ENIGMA\windows>cd ..
C:\msys64\ENIGMA>rem \ENIGMA\scripts\
C:\msys64\ENIGMA>cd ..
C:\msys64>rem \ENIGMA\
C:\msys64>cd ..
C:\>rem \
C:\>usr\bin\mintty.exe -w show /bin/env MSYSTEM=MINGW64 /bin/bash -l "C:\\ENIGMA\scripts\enigma.sh" win -64 --install --pro
Could not find specified path.
The problem, it turns out, is that extracting and simply running the files doesn't create the directory tree as the script actually searches for:> what is created > msys64/ENIGMA/_source ;; msys64/ENIGMA/windows
> what is needed > msys64/ENIGMA/scripts/windows
SOLUTION: rename _source to scripts, move windows into scripts folder
Say, what's the difference between std and pro? This isn't clear.
Another thing, is it intended to install packages even if you reply No?
Code: [Select]
Install BASE-DEVEL package?(Y/n)n
Cancelled
Installing needed packages..
For future reference, the default folder it'll download the git repo is msys/home/<your username>/msys64ENIGMA
Also got this:
Code: [Select]
Build Enigma?(Y/n)y
OK. Installing..
C:\msys64\ENIGMA\scripts\enigma.sh: line 171: cd: msys64ENIGMA/enigma-dev-64: No such file or directory
make: *** No rule to make target 'clean'. Pare.
make: *** No target and no make file found. Stop.
3
Issues Help Desk / Re: Cannot compile the source ("solved")
« on: April 15, 2019, 08:01:34 pm »
I only ran make. Was I supposed to run make all?
EDIT: Used that collection of .bat and script to install stuff. After running the x64 "install-or-update" ones, I've tried manually running make again. Now, here's something interesting:
Running MSYS2 MSYS, I got the same error as in the OP, which: no grpc_cpp_plugin in (/usr/local/bin:/usr/bin:/bin:/opt/bin:/c/Windows/System32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)
Running MSYS2 MinGW 32, I also got that error
Running MSYS2 MinGW 64, the compiling works, both the grpc plugin and g++
So there's also THAT to look out for, whether you're running msys2 or one of the mingw prompts.
EDIT: Used that collection of .bat and script to install stuff. After running the x64 "install-or-update" ones, I've tried manually running make again. Now, here's something interesting:
Running MSYS2 MSYS, I got the same error as in the OP, which: no grpc_cpp_plugin in (/usr/local/bin:/usr/bin:/bin:/opt/bin:/c/Windows/System32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)
Running MSYS2 MinGW 32, I also got that error
Running MSYS2 MinGW 64, the compiling works, both the grpc plugin and g++
So there's also THAT to look out for, whether you're running msys2 or one of the mingw prompts.
4
Issues Help Desk / Re: Cannot compile the source ("solved")
« on: April 15, 2019, 02:49:29 pm »
It's possible I only installed specific architecture libraries and didn't notice, which would explain why the plugin only worked with 32, while g++ only worked with 64, at least regarding that
Afterwards, I ran the line for the 64bit packages: pacboy -S git: toolchain:x make: boost:x protobuf:x libpng:x rapidjson:x pugixml:x yaml-cpp:x openal:x dumb:x libvorbis:x libogg:x flac:x mpg123:x libsndfile:x libgme:x sfml:x gtk2:x zlib:x libffi:x box2d:x bullet:x glew:x glm:x alure:x grpc:x - While running msys64. Immediately, running make gave the grpc_cpp_plugin error.
I will also note that I only ran this line after that first problem with grpc
I should probably test redoing everything I just did, but with msys32 from the beginning and the 32bit packages.
In the machine I managed this fix, I never installed msys before, so it's impossible the reason was any sort of leftovers.
What I think actually happened is you missed the crucial step in the MSYS2 installation procedure on their site where you restart MSYS2 and then continue the system upgrade a second time (I know MSYS2 setup is convoluted and messy and why I want to create an automated installer builder for ENIGMA)I followed that one to the letter. pacman -Syu, force close the window as the command line states, then open it again, run pacman -Su to finish it proper.
Afterwards, I ran the line for the 64bit packages: pacboy -S git: toolchain:x make: boost:x protobuf:x libpng:x rapidjson:x pugixml:x yaml-cpp:x openal:x dumb:x libvorbis:x libogg:x flac:x mpg123:x libsndfile:x libgme:x sfml:x gtk2:x zlib:x libffi:x box2d:x bullet:x glew:x glm:x alure:x grpc:x - While running msys64. Immediately, running make gave the grpc_cpp_plugin error.
I will also note that I only ran this line after that first problem with grpc
2. install grpc package:
for x86_64:
pacman -Sy mingw-w64-i686-grpc
I should probably test redoing everything I just did, but with msys32 from the beginning and the 32bit packages.
In the machine I managed this fix, I never installed msys before, so it's impossible the reason was any sort of leftovers.
Also, I should mention a community member has been maintaining an easy setup installation method for future reference.I'll try that one later today on another machine
https://enigma-dev.org/forums/index.php?topic=2954
5
Issues Help Desk / Cannot compile the source ("solved")
« on: April 15, 2019, 09:57:09 am »
Following the installation guide, this is what I get whenever I run make
Running on Windows 10, installed msys2 and followed all the steps of updating it before running the stuff in the wiki.
Quick edit: apparently, this is the culprit? https://github.com/grpc/grpc/issues/8774 - How do I work around this? Compile grpc and overwrite stuff in the msys folders?
PS: A bit off topic, but why not leave a link for the Discord channel in the homepage?
Edit2: Ok, I managed to make it work with something i can only see as a stupid oversight. That error above was running with msys-64. With 32, the plugin was found and it worked until it tried to run g++ (make[2]: g++: Command not found). At that failure, I ran make with the 64 again, and things followed without a problem. Seriously, what the fuck??
As a side note, someone should update the wiki to mention doing these things (pacman -Sy mingw-w64-grpc as per the linked thread + running make with msys32 first then with msys64), I doubt i'm the only one who suffered through this (exact same problem on 2 completely different win10 computers, no less).
Code: [Select]
$ make
make -C shared/protos/
make[1]: Entering directory '/d/enigma/enigma-dev/shared/protos'
which: no grpc_cpp_plugin in (/usr/local/bin:/usr/bin:/bin:/opt/bin:/c/Windows/System32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/)
make codegen
make[2]: Entering directory '/d/enigma/enigma-dev/shared/protos'
which: no grpc_cpp_plugin in (/usr/local/bin:/usr/bin:/bin:/opt/bin:/c/Windows/System32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/)
mkdir -p codegen/
protoc -I=. -I=/usr/include --cpp_out=codegen/ Action.proto
make[2]: protoc: Command not found
make[2]: *** [Makefile:35: codegen//Action.pb.cc] Error 127
make[2]: Leaving directory '/d/enigma/enigma-dev/shared/protos'
make[1]: *** [Makefile:47: lib] Error 2
make[1]: Leaving directory '/d/enigma/enigma-dev/shared/protos'
make: *** [Makefile:29: libProtocols] Error 2
Searched for "grpc_cpp_plugin" in the forum, found this thread, installed the packages, make still gives the same error. What's going on?Running on Windows 10, installed msys2 and followed all the steps of updating it before running the stuff in the wiki.
Quick edit: apparently, this is the culprit? https://github.com/grpc/grpc/issues/8774 - How do I work around this? Compile grpc and overwrite stuff in the msys folders?
PS: A bit off topic, but why not leave a link for the Discord channel in the homepage?
Edit2: Ok, I managed to make it work with something i can only see as a stupid oversight. That error above was running with msys-64. With 32, the plugin was found and it worked until it tried to run g++ (make[2]: g++: Command not found). At that failure, I ran make with the 64 again, and things followed without a problem. Seriously, what the fuck??
As a side note, someone should update the wiki to mention doing these things (pacman -Sy mingw-w64-grpc as per the linked thread + running make with msys32 first then with msys64), I doubt i'm the only one who suffered through this (exact same problem on 2 completely different win10 computers, no less).
Pages: 1