Author Topic: ERROR: Could not load in 2_CommandBrief-mb!  (Read 8032 times)

0 Members and 1 Guest are viewing this topic.

ERROR: Could not load in 2_CommandBrief-mb!
Received this error message attempting to play BluePlanet. fs2_open.log is attached.

Any ideas?

[attachment kidnapped by pirates]

 

Offline Jeff Vader

  • The Back of the Hero!
  • 212
  • Bwahaha
Re: ERROR: Could not load in 2_CommandBrief-mb!
You need the 2014 MediaVPs. They can be installed with the FSO installer or manually from this thread.
23:40 < achillion > EveningTea: ass
23:40 < achillion > wait no
23:40 < achillion > evilbagel: ass
23:40 < EveningTea > ?
23:40 < achillion > 2-letter tab complete failure

14:08 < achillion > there's too much talk of butts and dongs in here
14:08 < achillion > the level of discourse has really plummeted
14:08 < achillion > Let's talk about politics instead
14:08 <@The_E > butts and dongs are part of #hard-light's brand now
14:08 <@The_E > well
14:08 <@The_E > EvilBagel's brand, at least

01:06 < T-Rog > welp
01:07 < T-Rog > I've got to take some very strong antibiotics
01:07 < achillion > penis infection?
01:08 < T-Rog > Chlamydia
01:08 < achillion > O.o
01:09 < achillion > well
01:09 < achillion > I guess that happens
01:09 < T-Rog > at least it's curable
01:09 < achillion > yeah
01:10 < T-Rog > I take it you weren't actually expecting it to be a penis infection
01:10 < achillion > I was not

14:04 < achillion > Sometimes the way to simplify is to just have a habit and not think about it too much
14:05 < achillion > until stuff explodes
14:05 < achillion > then you start thinking about it

22:16 < T-Rog > I don't know how my gf would feel about Jewish conspiracy porn

15:41 <-INFO > EveningTea [[email protected]] has joined #hard-light
15:47 < EvilBagel> butt
15:51 < Achillion> yes
15:53 <-INFO > EveningTea [[email protected]] has quit [Quit: http://www.mibbit.com ajax IRC Client]

18:53 < Achillion> Dicks are fun

21:41 < MatthTheGeek> you can't spell assassin without two asses

20:05 < sigtau> i'm mining titcoins from now on

00:31 < oldlaptop> Drunken antisocial educated freezing hicks with good Internet == Finland stereotype

11:46 <-INFO > Kobrar [[email protected]] has joined #hard-light
11:50 < achtung> Surely you've heard of DVDA
11:50 < achtung> Double Vaginal Double ANal
11:51 < Kobrar> ...
11:51 <-INFO > Kobrar [[email protected]] has left #hard-light []

 
Re: ERROR: Could not load in 2_CommandBrief-mb!
Used the FSO installer for everything. I've got the 2014 Media VPs, was just using them to play the main campaign a few minutes ago.

 

Offline Jeff Vader

  • The Back of the Hero!
  • 212
  • Bwahaha
Re: ERROR: Could not load in 2_CommandBrief-mb!
Blue Planet expects to find them in /home/justin/gaming_misc/Freespace 2/mediavps_2014/ but isn't finding them. If you have them in some other folder, please make sure to move them to this path.
23:40 < achillion > EveningTea: ass
23:40 < achillion > wait no
23:40 < achillion > evilbagel: ass
23:40 < EveningTea > ?
23:40 < achillion > 2-letter tab complete failure

14:08 < achillion > there's too much talk of butts and dongs in here
14:08 < achillion > the level of discourse has really plummeted
14:08 < achillion > Let's talk about politics instead
14:08 <@The_E > butts and dongs are part of #hard-light's brand now
14:08 <@The_E > well
14:08 <@The_E > EvilBagel's brand, at least

01:06 < T-Rog > welp
01:07 < T-Rog > I've got to take some very strong antibiotics
01:07 < achillion > penis infection?
01:08 < T-Rog > Chlamydia
01:08 < achillion > O.o
01:09 < achillion > well
01:09 < achillion > I guess that happens
01:09 < T-Rog > at least it's curable
01:09 < achillion > yeah
01:10 < T-Rog > I take it you weren't actually expecting it to be a penis infection
01:10 < achillion > I was not

14:04 < achillion > Sometimes the way to simplify is to just have a habit and not think about it too much
14:05 < achillion > until stuff explodes
14:05 < achillion > then you start thinking about it

22:16 < T-Rog > I don't know how my gf would feel about Jewish conspiracy porn

15:41 <-INFO > EveningTea [[email protected]] has joined #hard-light
15:47 < EvilBagel> butt
15:51 < Achillion> yes
15:53 <-INFO > EveningTea [[email protected]] has quit [Quit: http://www.mibbit.com ajax IRC Client]

18:53 < Achillion> Dicks are fun

21:41 < MatthTheGeek> you can't spell assassin without two asses

20:05 < sigtau> i'm mining titcoins from now on

00:31 < oldlaptop> Drunken antisocial educated freezing hicks with good Internet == Finland stereotype

11:46 <-INFO > Kobrar [[email protected]] has joined #hard-light
11:50 < achtung> Surely you've heard of DVDA
11:50 < achtung> Double Vaginal Double ANal
11:51 < Kobrar> ...
11:51 <-INFO > Kobrar [[email protected]] has left #hard-light []

 
Re: ERROR: Could not load in 2_CommandBrief-mb!
So I was playing with wxLauncher.
Command line enabling 2014 MediaVPs mod: /home/justin/gaming_misc/Freespace 2/fs2_open_3.7.2_RC3 -mod MediaVPs_2014
Command line enabling Blue Planet: /home/justin/gaming_misc/Freespace 2/fs2_open_3.7.2_RC3 -mod blueplanet,mediavps_2014

Seriously? Seriously?!
wxLauncher/FSO installer folks,
LINUX FILESYSTEMS ARE CASE SENSITIVE
« Last Edit: August 07, 2014, 01:21:59 am by electrojustin »

 

Offline niffiwan

  • 211
  • Eluder Class
Re: ERROR: Could not load in 2_CommandBrief-mb!
gah - this is a case-sensitive filesystem issue :(  The installer installs to MediaVPs_2014 (and that location is controlled by the FSU/mediavpvs team) and Blueplanet is configured to use mediavps_2014. This doesn't matter except on Linux.  So either do what Jeff said and rename it to all lowercase, or change the blueplanet[2]/mod.ini files to reference the upper-case name.  Longer term I don't know what the better decision will be.

(and having just seen your most recent post, I need to re-iterate that it's actually the FSU/mediavps and Blueplanet teams that control the filename case here)
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: ERROR: Could not load in 2_CommandBrief-mb!
Although FSO really should be able to take a -mod mediavps_2014 commandline and locate a MediaVPs_2014 folder, seeing as how most of its file operations are case-insensitive, even on case-sensitive filesystems.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 
Re: ERROR: Could not load in 2_CommandBrief-mb!
Quote
Although FSO really should be able to take a -mod mediavps_2014 commandline and locate a MediaVPs_2014 folder, seeing as how most of its file operations are case-insensitive, even on case-sensitive filesystems.
Maybe internally case doesn't matter, but I don't know how FSO would magically divine the correct capitalization of MediaVPs_2014 when it goes to make the sys calls to load a file from that path.

Quote
This doesn't matter except on Linux.
I think this might effect Mac and BSD users as well, I always thought UNIX based operating systems had case sensitive files.

Quote
that location is controlled by the FSU/mediavpvs team
My apologies to the wxLauncher and FSO installer teams then.

How about setting a convention of some sort for the future :p?
A note to all modders and the FSU team then: ALWAYS USER LOWER CASE. Or at least make sure the mod ini is consistent. Also, as long as I'm ranting about filesystem differences, don't include slashes, forward or otherwise. I dunno what / does in windows, but in Linux paths it indicates going into a subdirectory, like \ does in windows. And spaces, quotation marks, and single quotes are a pain, because you sometimes have to escape those in some filesystems (like ext).

 

Offline jr2

  • The Mail Man
  • 212
  • It's prounounced jayartoo 0x6A7232
    • Steam
Re: ERROR: Could not load in 2_CommandBrief-mb!
There should be a way in Linux to mark a tree of subdirectories as case-insensitive.   =P  that would be great.

Edit

I suppose FSO could do a case-insensitive grep to get the correct case and then use that?
« Last Edit: August 07, 2014, 01:44:18 am by jr2 »

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: ERROR: Could not load in 2_CommandBrief-mb!
Quote
Although FSO really should be able to take a -mod mediavps_2014 commandline and locate a MediaVPs_2014 folder, seeing as how most of its file operations are case-insensitive, even on case-sensitive filesystems.
Maybe internally case doesn't matter, but I don't know how FSO would magically divine the correct capitalization of MediaVPs_2014 when it goes to make the sys calls to load a file from that path.
It doesn't need to "divine" anything; if there's more than one folder that matches, case-insensitively, then load all of them. It's not like FSO is unused to loading data from multiple directories.

There should be a way in Linux to mark a tree of subdirectories as case-insensitive.   =P  that would be great.
Well, you can always mount a FAT32 filesystem there.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 

Offline niffiwan

  • 211
  • Eluder Class
Re: ERROR: Could not load in 2_CommandBrief-mb!
Loading multiple locations is fine, loading them in the correct order would be more problematic.

Now, even though I kinda pointed the finger at the modders earlier I'm starting to think that was a bit unfair (sorry guys), after all you can practically only mod on Windows anyway and it's a bit unreasonable to expect a modder to know about the case sensitive Linux/BSD filesystem (since OSX I believe uses a case-preserving filesystem).  So maybe FSO could be changed to lookup the dir names insensitively (since it already does that inside VPs), or maybe the installer could convert all extracted dirs to lowercase, and maybe change the contents of all mod.ini primarylist & secondarylist lines to lowercase (for Linux/BSD only).
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: ERROR: Could not load in 2_CommandBrief-mb!
Loading multiple locations is fine, loading them in the correct order would be more problematic.
What correct order? If they were all meant to be in the same folder, they shouldn't be trying to override each other anyway.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 
Re: ERROR: Could not load in 2_CommandBrief-mb!
Quote
maybe the installer could convert all extracted dirs to lowercase
this

Quote
after all you can practically only mod on Windows
Why exactly is that? This sounds like something I should work towards rectifying if at all possible.

Quote
Well, you can always mount a FAT32 filesystem there.
eww

Linux has NTFS modules that come pre-installed with most distros if you want to go that route. It's journaling at least, but still oh god the fragmentation.

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: ERROR: Could not load in 2_CommandBrief-mb!
Quote
after all you can practically only mod on Windows
Why exactly is that? This sounds like something I should work towards rectifying if at all possible.
FRED2_Open is Windows-only. If you know any C/C++, wxFRED could always use more help (I've been meaning to take a look at the code myself one of these days, but I haven't found the time).
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 
Re: ERROR: Could not load in 2_CommandBrief-mb!
Quote
FRED2_Open is Windows-only. If you know any C/C++, wxFRED could always use more help

Really? wxFRED compiles and runs under Linux. No Makefiles though... :(

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: ERROR: Could not load in 2_CommandBrief-mb!
FRED2_Open and wxFRED are entirely separate projects.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 
Re: ERROR: Could not load in 2_CommandBrief-mb!
Quote
FRED2_Open and wxFRED are entirely separate projects.

Oh. So wxFRED works for Linux but is just bad to the point of unusable?
« Last Edit: August 07, 2014, 05:34:04 pm by electrojustin »

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: ERROR: Could not load in 2_CommandBrief-mb!
Quote
FRED2_Open and wxFRED are entirely separate projects.

Oh. So wxFRED works for Linux but is just bad to the point of unusable?
It's incomplete to the point of being literally unusable; last I heard, none of the GUI elements were coded to actually do anything yet.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 

Offline niffiwan

  • 211
  • Eluder Class
Re: ERROR: Could not load in 2_CommandBrief-mb!
Loading multiple locations is fine, loading them in the correct order would be more problematic.
What correct order? If they were all meant to be in the same folder, they shouldn't be trying to override each other anyway.

Ah... :nervous: you are probably correct  :D  I should try that with the mediavps_3612 since I know that their current installer setup results in two dirs with VPs in each :)


Quote
after all you can practically only mod on Windows
Why exactly is that? This sounds like something I should work towards rectifying if at all possible.

In addition to the FRED2/wxFRED issues that AdmiralRalwood mentioned, PCS2 is also quite unreliable on Linux.  It compiles and runs OK sometimes but crashes frequently.  And to make it more ~fun~, it's random.  Sometimes a model will open fine, other times the same model will crash on load. And then when I ran it in a debugger, it didn't crash at all  :sigh:
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...

 
Re: ERROR: Could not load in 2_CommandBrief-mb!
Quote
And then when I ran it in a debugger, it didn't crash at all  :sigh:

GDB disables ASLR (Address Stack Layout Randomization, or something like that. It's a security "feature" to make stack smashing harder). This sounds like the kind of randomness that comes with buffer overflows. Have you tried running valgrind or memcheck on it to see if it turns up with anything?

Edit: In case you were curious, the reason ASLR is important is because AFAIK it's implemented as just some random stack pushes. So a buffer overflow might result in junk data being overwritten or something important like the saved instruction pointer being overwritten, resulting in the crash. Has running it from the command line ever resulted in an error message along the lines of "stack smashing detected"?
Also, Valgrind might make the program run pretty slow, so it could be worth looking into compiling it with gcc stack protection to see where/when the buffer overflows actually occur. But I digress quite a bit, this is probably a discussion for a proper bug report somewhere other than the BluePlanet subforum.

Quote
It's incomplete to the point of being literally unusable; last I heard, none of the GUI elements were coded to actually do anything yet.
This. I just checked the source and everything in the editors directory is like 10 lines of code, so I'm guess it was all just framework and placeholder code. Running the application doesn't even result in a blank mission, it just tiles my GTK default background and gives me some buttons to push, which of course don't do anything.
« Last Edit: August 08, 2014, 02:32:40 pm by electrojustin »