Show Posts
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 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 »
211
Announcements / Re: Main Progress [Stalled because we can't Git]
« on: February 27, 2012, 02:09:40 pm »
I like these ideas. I just want to mention that we should also consider offline alternatives. I think the download page should provide an Online ENIGMA and an Offline ENIGMA. The prior will download and install things on the fly, like we've been talking about. The offline version will include everything up front (we might be able to offer a web form with checkboxes for the components that they want and don't want, and then assemble a package for them).
Obviously not a big priority right now, but we should keep it in mind for down the road.
Obviously not a big priority right now, but we should keep it in mind for down the road.
212
Announcements / Re: Main Progress [Stalled because we can't Git]
« on: February 27, 2012, 02:10:41 am »
Just wanted to mention that I just fixed a bunch of stuff with the Plugin (improved APNG, so sprites in EGM don't fail so much), and added a couple wiki pages.
Josh and I are undecided on what to do about Rusky's decision to delete Josh's custom alure-related stuff.
Josh says that he doesn't think he can just have alure in its own git repository and/or stick it in a subproject or binary or whatever.
Cheeseboy seems to be glad that it's gone, and claims that this somehow means that enigma suddenly now supports mp3. I'm hoping to investigate this claim. Maybe learn something about alure in the process.
I am generally of the opinion that Rusky had *some* sort of reason to delete it. It takes a lot of steps to delete something like that from the repository, it's not like you can just accidentally hit the delete key.
Unfortunately, there are strong rumors that Rusky is going to be gone for a long time (possibly more than a year). This means that we're probably going to have to forge our own path, even if that means re-integrating Josh's alure stuff back into the repository (although I hope it doesn't come to that).
If and when Rusky comes back, I want him to see this project, and say "Wow, you didn't do half bad." rather than "You idiots. Now the repository looks like a bomb hit it. No wonder it takes a decade to checkout/update"
Josh and I are undecided on what to do about Rusky's decision to delete Josh's custom alure-related stuff.
Josh says that he doesn't think he can just have alure in its own git repository and/or stick it in a subproject or binary or whatever.
Cheeseboy seems to be glad that it's gone, and claims that this somehow means that enigma suddenly now supports mp3. I'm hoping to investigate this claim. Maybe learn something about alure in the process.
I am generally of the opinion that Rusky had *some* sort of reason to delete it. It takes a lot of steps to delete something like that from the repository, it's not like you can just accidentally hit the delete key.
Unfortunately, there are strong rumors that Rusky is going to be gone for a long time (possibly more than a year). This means that we're probably going to have to forge our own path, even if that means re-integrating Josh's alure stuff back into the repository (although I hope it doesn't come to that).
If and when Rusky comes back, I want him to see this project, and say "Wow, you didn't do half bad." rather than "You idiots. Now the repository looks like a bomb hit it. No wonder it takes a decade to checkout/update"
213
Issues Help Desk / Re: Help With Installation Requested
« on: February 27, 2012, 01:55:15 am »
No, no. It's an extra program that's pretty much unrelated to enigma.
Technically speaking:
SvnKit is a self-contained library that ENIGMA uses to automatically download and update itself.
Svn is a version management software. It's what we use ENIGMA with to make it so that we can have different versions of code at the same time, with some more updated than others. SvnKit kind of talks with this to decide if it needs updates, and to grab them (but you don't need SVN, because it's already pretty much contained inside SvnKit).
My *guess* is that SvnKit somehow screwed up a little bit and didn't download things correctly, and is now very confused, so it doesn't know how to proceed. As such, I want to go in manually and find out what's going on, and try to fix it. Since SvnKit is only an automated library tool, manual stuff requires Svn instead, and I don't think we can use the one inside SvnKit.
Now here's the simple version:
I want you to install an Svn client. It's completely optional, and won't interact with ENIGMA at all. We're going to use it to manually diagnose/fix your problem. Once we're done fixing your repository, you can either keep Svn or uninstall it. It will not run in the background.
That is, if you're interested. Otherwise, you'll have to wait until we get the Windows install working again (which might be a while).
This page will tell you everything you ever wanted to know about version control, but most importantly, where to get a client:
http://enigma-dev.org/docs/Wiki/Revision_control
Once you have downloaded and installed a client (like TortoiseSVN), you then will want to add the binaries to your PATH variable (they should be inside of wherever you installed the client to, in a "bin/" folder. So just add the full path to that "bin" folder, including the "bin" part, to your PATH variable.
Once that's done, you should be able to open a Command Console and type "svn" and it will output something like "Type 'svn help' for usage."
Technically speaking:
SvnKit is a self-contained library that ENIGMA uses to automatically download and update itself.
Svn is a version management software. It's what we use ENIGMA with to make it so that we can have different versions of code at the same time, with some more updated than others. SvnKit kind of talks with this to decide if it needs updates, and to grab them (but you don't need SVN, because it's already pretty much contained inside SvnKit).
My *guess* is that SvnKit somehow screwed up a little bit and didn't download things correctly, and is now very confused, so it doesn't know how to proceed. As such, I want to go in manually and find out what's going on, and try to fix it. Since SvnKit is only an automated library tool, manual stuff requires Svn instead, and I don't think we can use the one inside SvnKit.
Now here's the simple version:
I want you to install an Svn client. It's completely optional, and won't interact with ENIGMA at all. We're going to use it to manually diagnose/fix your problem. Once we're done fixing your repository, you can either keep Svn or uninstall it. It will not run in the background.
That is, if you're interested. Otherwise, you'll have to wait until we get the Windows install working again (which might be a while).
This page will tell you everything you ever wanted to know about version control, but most importantly, where to get a client:
http://enigma-dev.org/docs/Wiki/Revision_control
Once you have downloaded and installed a client (like TortoiseSVN), you then will want to add the binaries to your PATH variable (they should be inside of wherever you installed the client to, in a "bin/" folder. So just add the full path to that "bin" folder, including the "bin" part, to your PATH variable.
Once that's done, you should be able to open a Command Console and type "svn" and it will output something like "Type 'svn help' for usage."
214
Issues Help Desk / Re: Help setting up Windows Git Install
« on: February 27, 2012, 01:36:51 am »
Let's see if JoshDreamland knows anything about this, because this is out of my range of expertise.
The first pastebin looks like (my best guess) you may be missing some dependencies, like zlib? Idunno.
The second pastebin actually looks somewhat normal to me, at least the part about "Could not open", as I usually see those errors, but everything works fine.
The one that does concern me is "Parse fail". You will notice that the path is all screwed up. cheeseboy has complained about a similar problem. We've played with that a bit, but I don't know that anything made it into the repository.
Just to share my output when I run lgm:
So as you can see, those don't seem to give us any indication of the real issue, because I have a very similar output, but it still works fine for me.
The first pastebin looks like (my best guess) you may be missing some dependencies, like zlib? Idunno.
The second pastebin actually looks somewhat normal to me, at least the part about "Could not open", as I usually see those errors, but everything works fine.
The one that does concern me is "Parse fail". You will notice that the path is all screwed up. cheeseboy has complained about a similar problem. We've played with that a bit, but I don't know that anything made it into the repository.
Just to share my output when I run lgm:
Code: [Select]
...
Parsing settings...
Could not open ENIGMAsystem/SHELL/Graphics_Systems/OpenGL/Config/xlib.ey.
Could not open ENIGMAsystem/SHELL/Widget_Systems/None/Config/xlib.ey.
Could not open ENIGMAsystem/SHELL/Audio_Systems/OpenAL/Config/xlib.ey.
Parse fail: Could not open compiler descriptor `Compilers/Linux/Compilers/Linux/clang.ey.ey`.
...So as you can see, those don't seem to give us any indication of the real issue, because I have a very similar output, but it still works fine for me.
215
Issues Help Desk / Re: Help With Installation Requested
« on: February 26, 2012, 12:13:33 am »
It does appear as though you have run into some weird SVN error, judging by the "incomplete C:\ENIGMA-R4-r915-win" message immediately before the SvnKit error.
And this occurs every time that you do a fresh install? How odd.
Do you have an SVN client installed?
Also, I'm helping Harri out with his zip, so maybe we can get you working from that end instead.
And this occurs every time that you do a fresh install? How odd.
Do you have an SVN client installed?
Also, I'm helping Harri out with his zip, so maybe we can get you working from that end instead.
216
Issues Help Desk / Re: Help setting up Windows Git Install
« on: February 26, 2012, 12:07:08 am »Quote
Old version of what? LGM? That is what I was referring to when I said about the error the first time. Or old ENIGMA.exe? Because that I just created compiling the codeblocks project inside the stupidity-buffer.Uh, sorry, old version of enigma.jar. I just realized that I hadn't actually compiled and uploaded the latest jar, which is why you were still using the "old" version. Anyways, I've uploaded it now. Simply redownload enigma.jar and replace.
I was able to run it fine on Linux fairly recently. Let me try again with the latest everything.
Edit: Just ran it again. Nothing fancy, just a 1-room game with no objects or anything. Runs great. Had to change the sound system to None, rather than OpenAL, because of the alure issue. If you want me to try a more complex game like the clown example, just say so.
217
Issues Help Desk / Re: Help setting up Windows Git Install
« on: February 25, 2012, 08:31:39 pm »
As far as I'm aware, the .ey file will not be repopulated if it already exists. You will need to delete the .ey file. Obviously you'll need to shut down LGM/Enigma before doing this, and then run ENIGMA.exe again once the file has been deleted. ENIGMA.exe will create its own ey file.
Also looks like you're still using the older revision. Not a big deal, I'll help with it anyways. The latest just improves error handling so that LGM doesn't freeze up.
Also looks like you're still using the older revision. Not a big deal, I'll help with it anyways. The latest just improves error handling so that LGM doesn't freeze up.
219
Issues Help Desk / Re: Help With Installation Requested
« on: February 25, 2012, 06:58:54 pm »
Please share the latest error.
220
Announcements / Re: Main Progress [Stalled because we can't Git]
« on: February 25, 2012, 06:56:25 pm »
A discussion about getting Windows Git Install working (primarily between Harrikiri and myself) has been split from this topic to here: http://enigma-dev.org/forums/index.php?topic=945.0
221
Issues Help Desk / Re: Help setting up Windows Git Install
« on: February 25, 2012, 06:53:36 pm »
The ey file shouldn't be empty. I would strongly encourage that you get ENIGMA.exe working. Share whatever errors you're encountering there and we'll see if we can help with that.
222
Issues Help Desk / Re: Help setting up Windows Git Install
« on: February 25, 2012, 06:25:26 pm »
The error looks exactly like an error I was working on recently. Here's a summary:
Prior to revision b8e976a (just committed yesterday), if the Compiler Description file (gcc.ey) was missing, LGM would freeze and report an error similar to that - An ExceptionInInitializerError caused by IndexOutOfBoundsException caused by trying to fetch an ArrayList index from inside of TargetHandler. On or after revision b8e976a, LGM should no longer freeze, but ENIGMA will report an error trying to set up Compilers stuff while calling Make. This is more or less intended behavior. If the Compiler Description is missing, I don't know what compiler to use to build ENIGMA, and will throw an error about it.
tl;dr: Compilers/Windows/gcc.ey is missing. Why is it missing? Did you remember to run ENIGMA.exe instead of lgm16b4.jar? Also, looks like you're using a slightly outdated version of ENIGMA.
Prior to revision b8e976a (just committed yesterday), if the Compiler Description file (gcc.ey) was missing, LGM would freeze and report an error similar to that - An ExceptionInInitializerError caused by IndexOutOfBoundsException caused by trying to fetch an ArrayList index from inside of TargetHandler. On or after revision b8e976a, LGM should no longer freeze, but ENIGMA will report an error trying to set up Compilers stuff while calling Make. This is more or less intended behavior. If the Compiler Description is missing, I don't know what compiler to use to build ENIGMA, and will throw an error about it.
tl;dr: Compilers/Windows/gcc.ey is missing. Why is it missing? Did you remember to run ENIGMA.exe instead of lgm16b4.jar? Also, looks like you're using a slightly outdated version of ENIGMA.
223
Issues Help Desk / Re: Help With Installation Requested
« on: February 25, 2012, 06:18:45 pm »
That's fine. You're always welcome to do that and support it yourself. I just don't know what you put in it or such, so I probably can't help other people using it if something goes wrong - unless I happen to recognize the error message.
224
Issues Help Desk / Re: Help With Installation Requested
« on: February 25, 2012, 06:11:26 pm »
I'd just like to point out that I can only help with the default installation from the download/install page. I cannot help with Harri's zip.
From your first error (the one you took a screenshot of), you are experiencing multiple problems. The first is that SvnKit is missing. Please confirm that "C:\Program Files\!Game Creation Software\ENIGMA-R4-r915-win\plugins\shared\svnkit.jar" exists. If it does, I suspect an issue with the path name (you should not have an exclamation mark in the path name, "!Game Creation Software" is not good, like Harri said. Try installing to C:\ENIGMA-R4-r915-win instead. Then report your progress.
Also, you shouldn't need to wait 2 hours. Once you see
From your first error (the one you took a screenshot of), you are experiencing multiple problems. The first is that SvnKit is missing. Please confirm that "C:\Program Files\!Game Creation Software\ENIGMA-R4-r915-win\plugins\shared\svnkit.jar" exists. If it does, I suspect an issue with the path name (you should not have an exclamation mark in the path name, "!Game Creation Software" is not good, like Harri said. Try installing to C:\ENIGMA-R4-r915-win instead. Then report your progress.
Also, you shouldn't need to wait 2 hours. Once you see
Quote
Exception in thread blahThat's an error, and no amount of waiting is going to fix it. Report it.
at org.enigma.blah
at org.enigma.blah
blah blah blah
225
Issues Help Desk / Re: Help setting up Windows Git Install
« on: February 25, 2012, 06:00:29 pm »
HaRRiKiRi: Please try to follow the instructions on http://enigma-dev.org/docs/Wiki/Install:Git . Note that you will find the latest LGM.jar there.