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.


Messages - Goombert

1921
Issues Help Desk / Re: GMX Reader
« on: January 19, 2014, 09:26:21 PM »
Wait, damn you responded too fast before I could edit that. Josh said it is a Java setting, let me Google.

Basically you have Java Preferences set to not allow Java Apps to utilize a certain amount of memory, LGM uses anywhere between 60,000K on startup to 356,000K is the maximum I've seen it use, bout the same as Eclipse Java IDE that I use when coding LGM.

Edit: Follow the instructions here...
http://www.rcsb.org/pdb/staticHelp.do?p=help/viewers/appletMemory.html

Those might be incorrect, I am trying to find it, there's instructions somewhere.
https://www.google.com/#q=java+preferences+ram+

Edit 2:
Looks like you could open up settings.ini and change target parameter to the following.

Quote
idecommand="java -jar -Xms256m -Xmx512m"

1922
Issues Help Desk / Re: GMX Reader
« on: January 19, 2014, 09:24:23 PM »
Alright, give me some time to look into it further, because I honestly have no ideas right now.

1923
General ENIGMA / Re: Linking Exception Draft
« on: January 19, 2014, 06:53:54 PM »
I would have considered this a general ENIGMA topic, and I am going to move it there.

1924
Issues Help Desk / Re: GMX Reader
« on: January 19, 2014, 04:21:39 PM »
Doesn't make sense you have 2GB ram. All it looks like it's saying is Java ran out of memory from loading a really large background. I loaded the project fine though with a 4GB ram, but doesn't make sense. Try updating both LGM and the plugin, and your actual Java install, it might actually be a JDK bug.

1925
Issues Help Desk / Re: GMX Reader
« on: January 19, 2014, 02:50:50 PM »
Ok can you open All Programs and type dxdiag and hit enter, run that program, save the information to a text file, and http://pastie.org that for me. I need to see your computers hardware specs.

1926
Issues Help Desk / Re: There was an issue loading the project
« on: January 19, 2014, 02:03:00 PM »
I just fixed it, it was a plugin bug, once again, egofree please update the LGM and plugin jar files with the fixed version.
http://enigma-dev.org/docs/Wiki/Install:Extra_Packages

This was the commit that fixed the paths causing the EGM corruption.
https://github.com/enigma-dev/lgmplugin/commit/c5d181a1c76a1569554f23d2f7e425749e71b550

I have also updated the Portable ZIP.
http://enigma-dev.org/docs/Wiki/Install:Windows

Again, let me know if the issue is fixed.

But Harri, wow, I never realized that, but they aren't necessarily game backup either, every body on Google just says they are a backup, but I can't find anything on what the extension stood for. I wonder where I got the idea to call them global backup? But I guess game backup does make more sense.
https://www.google.com/#q=gb1+file

I can't even find a result of IsmAvatar or LGM, though I could have swore she called them a global backup too.

1927
Issues Help Desk / Re: Views not working
« on: January 19, 2014, 01:32:50 PM »
Alright Josh will need to fix it and apply the code to the other graphics system. I am not sure what all he's doing today but once he fixes that bug I can move the code over so that all the other graphics systems are fixed. I am currently trying to fix a severe bug in our EGM format reader.

1928
Issues Help Desk / Re: There was an issue loading the project
« on: January 19, 2014, 01:09:46 PM »
The issue is the path resource ego, I am working on fixing it now this is a really illusive bug.

Don't worry about the gb files, those are global backup files, or rather just GMK's that are saved each time you save your project in case of corruption, I am going to add a preference to turn it off.

1929
Issues Help Desk / Re: Views not working
« on: January 19, 2014, 01:07:58 PM »
Try going to Build->Settings and turn on OpenGL3, Josh was just in there attempting to clean up our view code which got a little messy.

1930
Issues Help Desk / Re: There was an issue loading the project
« on: January 19, 2014, 03:05:13 AM »
egofree, this appears to have been the GMX Reader and Writer handling the GUID incorrectly, I fixed it now properly and thoroughly tested converting your game to an EGM and it works just as expected.

Please update both LateralGM and the Plugin jars which you can obtain from the Extra Packages page.
http://enigma-dev.org/docs/Wiki/Install:Extra_Packages#LateralGM
If you do not wish to manually replace the files, you can simply download the updated Portable Zip on Windows.
http://enigma-dev.org/docs/Wiki/Install:Windows

I hope this fixes the issue, please let me know if it does.

1931
Developing ENIGMA / Re: New feature: Complex Polygons (review requested)
« on: January 18, 2014, 04:19:29 PM »
Confirmed working here, thanks for the quick fix sorlok!

1932
Developing ENIGMA / Re: New feature: Complex Polygons (review requested)
« on: January 18, 2014, 02:09:11 PM »
Yes I am unable to build GL1 now as well, though, you can't blame sorlock, whoever merged it without testing is to blame, but it's fine anyway, just hurry up and make a fix you guys.

1933
Issues Help Desk / Re: There was an issue loading the project
« on: January 18, 2014, 12:09:07 PM »
Hello egofree, I have just attempted to load your project and did so without any errors. There appeared to be no issues with the project and there were no exception messages reported in the output log.


The rooms also appeared fine.


Perhaps, you should try using the LGM from the extra packages page, something may be messed up and perhaps you obtained an older version.
http://enigma-dev.org/docs/Wiki/Install:Extra_Packages

1934
Alright, looks like I failed pretty miserably at this one, at any rate, as you can on the site tracker, Josh just committed his fix which I am testing now, please try git update and test his version of the fixes, he tested on Linux, I am going to test from Windows.

This is his commit.
https://github.com/enigma-dev/enigma-dev/commit/b539ff0bee4b085532d8d0782d2518f83022ba3a

1935
Go to that file and line and change that call to GetVertexStride() :p

Josh is also attempting to fix it right now.