Skip to main content ↑ ↓
Topic: neoSphere 5.10.1 (Read 8877789 times) previous topic - next topic
0 Members and 29 Guests are viewing this topic.

Re: minisphere 1.6.1

Reply #780 –
Allegro's handling of audio format libs when building is dumb.  There are certain flags you have to set in CMake to get it to work right.  It's easier I've found to use cmake-gui.

Re: minisphere 1.6.1

Reply #781 –
Follow-up: Do you have the necessary libraries installed?  For full audio support you need:

* libvorbis
* libvorbisfile
* libogg
* dumb
* libflac

Re: minisphere 1.6.1

Reply #782 –
I downloaded this a few days ago and I could run Sphere Studio just fine (even though I ran into problems trying to actually make anything), but now it doesn't even launch at all. When I try to run it just doesn't open. Help?

Re: minisphere 1.6.1

Reply #783 –
Something probably got corrupted.  Delete MyDocuments/SphereStudio/Settings and try again.

Re: minisphere 1.6.1

Reply #784 –
Everyone: Next release will change the debugger semantics (allowing a debugger to be attached at any time) and include a debug-enabled build of Sphere Studio. :)

Edit: Also in the pipeline: ArrayBuffer support.  I bit the bullet and procured the latest build of Duktape to enable this.  From what I've seen, the Duktape master is extremely well-tested, so I'm not too concerned about catastrophic bugs there. :)  There are also supposed to be some performance improvements in the latest builds!

Re: minisphere 1.6.1

Reply #785 –
Quote from: Lord English – on

Something probably got corrupted.  Delete MyDocuments/SphereStudio/Settings and try again.

Deleting the whole folder did the trick.

EDIT: But now when I try to add files to my project, it gives me unhandled exception errors about "illegal characters in path" and "Object reference not set to an instance of an object". When I try adding a spriteset it says "Can't load spriteset: ?.rss".

Re: minisphere 1.6.1

Reply #786 –
The spriteset creation is probably a bug caused by my recent changes (it's going through a bit of upheaval at the moment), I'll look into it.  Not sure about the illegal filename characters though...  That seems weird.

Re: minisphere 1.6.1

Reply #787 –
Quote from: Lord English – on

The spriteset creation is probably a bug caused by my recent changes (it's going through a bit of upheaval at the moment), I'll look into it.  Not sure about the illegal filename characters though...  That seems weird.

I guess I'll use the editor provided with Sphere 1.5 for now. I just need to figure out how to get it to work with Minisphere.

Re: minisphere 1.6.1

Reply #788 –
You MIGHT be able to use a stock installation of Sphere 1.5 and copy minisphere's engine.exe over the 1.5 one.  That should work.

Re: minisphere 1.6.1

Reply #789 –
Hey guys, see the screenshot below for what you have to look forward to! ;D

Having a Sphere debugger is so awesome.

Re: minisphere 1.6.1

Reply #790 –
Literally the very best thing from a new Sphere engine and editor combination. This is just really awesome! :)
If you use code to help you code you can use less code to code. Also, I have approximate knowledge of many things.

Sphere-sfml here
Sphere Studio editor here

Re: minisphere 1.6.1

Reply #791 –
The new Duktape build also seems to be a lot faster--game startup is now on par with Sphere 1.5 now, even for large games like Aquatis which used to take up to 5 seconds to compile all the scripts.

Re: minisphere 1.6.1

Reply #793 –
minisphere 1.7 is out!

So... anyone care to test out the new debugger? ;)
 

Re: minisphere 1.7.1

Reply #794 –
Well, that didn't take long... I had to bump to 1.7.1 because I forgot to include a Duktape fix for improper breakpoint triggering in 1.7.0 (breakpoints inside if statements would trigger even if the condition itself wasn't hit).