HLP Network

News:

HLP Donations Page has been reworked for supporting the site.
Please note that the previous "Tiers" are currently not operational (but will be worked on).
You can still cancel any previous re-occurring donations to make new ones which will go to the new Treasurer Admin (Zacam).

 
« Previous Thread Next Thread »
Print
Pages: [1] 2 Next >   Go Down

Author Topic: 70 warnings when starting up a mod for freespace open  (Read 3745 times)

0 Members and 1 Guest are viewing this topic.

Offline Silent Fox 104

  • 24
70 warnings when starting up a mod for freespace open
on: August 16, 2014, 11:55:43 am
Hey if anyone could help me get around this problem would be much appreciated, thanks.

I am having problems with Blueplanet 2 and other mods, as you can see in the attached screenshot I get over 70 warnings. I Also can get in to Blueplanet 2 but it won't start anything but the intro and the main menu.

[attachment kidnapped by pirates]
 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: 70 warnings when starting up a mod for freespace open
Reply #1 on: August 16, 2014, 11:57:38 am
Please post your fs2_open.log file.  Instructions on how to do this can be found in this post.

(Although if I had to guess, I'd say it sounds like it's not finding the MediaVPs. Post your log anyway so we can be sure.)
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 Silent Fox 104

  • 24
Re: 70 warnings when starting up a mod for freespace open
Reply #2 on: August 16, 2014, 12:26:47 pm
Alright I managed to find it.

[attachment kidnapped by pirates]
 

Offline Yarn

  • 210
Re: 70 warnings when starting up a mod for freespace open
Reply #3 on: August 16, 2014, 01:13:08 pm
First of all, your version of FSO (3.6.12) is very old. Blue Planet (and may other mods) requires a recent build, such as 3.7.2 RC4. (A recent build is strongly recommended anyway, even if you're not playing any mods.) Once you get that, make sure you remove these command-line parameters since they are now deprecated: -env, -glow, -spec, -normal

Next, make sure that you have the 2014 MediaVPs installed to a folder called MediaVPs_2014. If you still get errors, go into the blueplanet and blueplanet2 folders, open the mod.ini files, and change "mediavps_2014" to MediaVPs_2014".
"Your fighter is running out of oil.  Please check under the hood and add more if necessary"
--strings.tbl, entry 177

"Freespace is very tired.  It is shutting down to get some rest."
--strings.tbl, entry 178
 

Offline Silent Fox 104

  • 24
Re: 70 warnings when starting up a mod for freespace open
Reply #4 on: August 16, 2014, 01:26:22 pm
wow who would have thought changing the name of a file could make such a difference, thanks a lot for the help!

everything is working now
 

Offline Jeff Vader

  • The Back of the Hero!
  • Moderator
  • 212
  • Bwahaha
Re: 70 warnings when starting up a mod for freespace open
Reply #5 on: August 16, 2014, 02:04:10 pm
FSO: you gotta be gentle with it. Just like a Swedish lady.
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 []
 

Offline Silent Fox 104

  • 24
Re: 70 warnings when starting up a mod for freespace open
Reply #6 on: August 16, 2014, 05:20:47 pm
Okay, now something else is wrong now every mod I start now opens like blueplanet and I can't seem to get it back to regular freespace 2.

Any thoughts on this?
 

Offline Silent Fox 104

  • 24
Re: 70 warnings when starting up a mod for freespace open
Reply #7 on: August 16, 2014, 05:25:14 pm
here is my log file again, hope it helps

[attachment kidnapped by pirates]
 

Offline Yarn

  • 210
Re: 70 warnings when starting up a mod for freespace open
Reply #8 on: August 16, 2014, 05:39:57 pm
Code: [Select]
Found root pack '/Applications/Freespace/mediavps_2014/MV_Advanced.vp' with a checksum of 0x4b8b0f5a
Found root pack '/Applications/Freespace/mediavps_2014/MV_AnimGlows.vp' with a checksum of 0x6a554026
Found root pack '/Applications/Freespace/mediavps_2014/MV_Assets.3612.vp' with a checksum of 0x59649c21
Found root pack '/Applications/Freespace/mediavps_2014/MV_Assets.vp' with a checksum of 0x529cc70f
Found root pack '/Applications/Freespace/mediavps_2014/MV_CB_ANI_1.vp' with a checksum of 0x9c948078
Found root pack '/Applications/Freespace/mediavps_2014/MV_CB_ANI_2.vp' with a checksum of 0xd1e3fc51
Found root pack '/Applications/Freespace/mediavps_2014/MV_Effects.3612.vp' with a checksum of 0x9c510aa0
Found root pack '/Applications/Freespace/mediavps_2014/MV_Effects.vp' with a checksum of 0xb9a9a485
Found root pack '/Applications/Freespace/mediavps_2014/MV_Music.vp' with a checksum of 0xb3e21469
Found root pack '/Applications/Freespace/mediavps_2014/MV_RadarIcons.vp' with a checksum of 0x31dd7781
Found root pack '/Applications/Freespace/mediavps_2014/MV_Root.3612.vp' with a checksum of 0x7c9d7e74
Found root pack '/Applications/Freespace/mediavps_2014/MV_Root.vp' with a checksum of 0x6ffd5c78
These are the 3.6.12 MediaVPs, not the 2014 MediaVPs. Please rename this folder to "mediavps_3612", then make a new folder called "MediaVPs_2014" and place the 2014 MediaVPs there.

Code: [Select]
Deprecated flag '-spec' found. Please remove from your cmdline.
Deprecated flag '-glow' found. Please remove from your cmdline.
Deprecated flag '-normal' found. Please remove from your cmdline.
Deprecated flag '-env' found. Please remove from your cmdline.
As I said in the last post, these are deprecated, so they should be removed.
"Your fighter is running out of oil.  Please check under the hood and add more if necessary"
--strings.tbl, entry 177

"Freespace is very tired.  It is shutting down to get some rest."
--strings.tbl, entry 178
 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: 70 warnings when starting up a mod for freespace open
Reply #9 on: August 16, 2014, 06:39:49 pm
Quote from: Silent Fox 104 on August 16, 2014, 05:20:47 pm
Okay, now something else is wrong now every mod I start now opens like blueplanet and I can't seem to get it back to regular freespace 2.

Any thoughts on this?
Well, according to your debug log, that's because blueplanet2 is the currently-selected mod:
Code: [Select]
-mod blueplanet2,blueplanet,mediavps_2014
Are you sure you're actually activating another mod in the launcher? And then running FSO through the launcher, not just launching the executable by itself?
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 Silent Fox 104

  • 24
Re: 70 warnings when starting up a mod for freespace open
Reply #10 on: August 16, 2014, 07:19:33 pm
Ok I have two files now one is MediaVPs_2014 and the other is the mediavps_3616. I'm using a Mac for all this and it was not easy to get everything together. once again I have attached a screenshot and my Fs2_open.log again. I've double checked all the media files and made sure their in the right folder, so I don't know what wrong?

I also noticed that the installer for some reason didn't download everything so I've had to individually download the remnants myself . . . which wasn't fun.

like I said before it was stuck on blueplanet 1 and 2, every time I tried to play a different mod. but now nothing works again.

The mystery continues . . .

[attachment kidnapped by pirates]
  

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: 70 warnings when starting up a mod for freespace open
Reply #11 on: August 16, 2014, 07:26:14 pm
That error is because:
Quote from: Yarn on August 16, 2014, 01:13:08 pm
Blue Planet (and may other mods) requires a recent build, such as 3.7.2 RC4.
To be precise, the 2014 MediaVPs (used by the most recent release of Blue Planet and many other mods) require a version of FSO newer than 3.7.0.

Quote from: Silent Fox 104 on August 16, 2014, 07:19:33 pm
like I said before it was stuck on blueplanet 1 and 2, every time I tried to play a different mod.
How are you trying to play different mods, exactly?
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 Yarn

  • 210
Re: 70 warnings when starting up a mod for freespace open
Reply #12 on: August 16, 2014, 09:01:15 pm
Quote from: Silent Fox 104 on August 16, 2014, 07:19:33 pm
...and the other is the mediavps_3616.
Wrong. It's supposed to be mediavps_3612. A large number of mods depend on that folder having that name.

Quote from: Silent Fox 104 on August 16, 2014, 07:19:33 pm
I also noticed that the installer for some reason didn't download everything so I've had to individually download the remnants myself . . . which wasn't fun.
Yeah, lots of other people have reported that too. I don't know exactly what the cause is, but I think that server overload is (still) partly to blame.
"Your fighter is running out of oil.  Please check under the hood and add more if necessary"
--strings.tbl, entry 177

"Freespace is very tired.  It is shutting down to get some rest."
--strings.tbl, entry 178
 

Offline Silent Fox 104

  • 24
Re: 70 warnings when starting up a mod for freespace open
Reply #13 on: August 16, 2014, 09:50:52 pm
My bad the folder is called mediavps_3612

Also the FS_Open 3.7.2 RC4 files that I just got don't look right to me I'll attach a screenshot of them with this.

I'm using the wxlauncher if that helps.

[attachment kidnapped by pirates]
 

Offline Silent Fox 104

  • 24
Re: 70 warnings when starting up a mod for freespace open
Reply #14 on: August 16, 2014, 10:05:22 pm
This might help as well, this is what my set-up looks like.

[attachment kidnapped by pirates]
 

Offline Yarn

  • 210
Re: 70 warnings when starting up a mod for freespace open
Reply #15 on: August 16, 2014, 11:02:07 pm
This isn't related to this issue, but the movies folder is supposed to go inside the data folder.
"Your fighter is running out of oil.  Please check under the hood and add more if necessary"
--strings.tbl, entry 177

"Freespace is very tired.  It is shutting down to get some rest."
--strings.tbl, entry 178
 

Offline Silent Fox 104

  • 24
Re: 70 warnings when starting up a mod for freespace open
Reply #16 on: August 16, 2014, 11:14:45 pm
Ok just did that.

also another thing I need to mention is that I get a black screen when I try to run a mod or just the regular FS2 that leads me to have to turn off my Mac.
 

Offline Echelon9

  • 210
Re: 70 warnings when starting up a mod for freespace open
Reply #17 on: August 17, 2014, 12:16:42 am
Hi Silent Fox 104,

I'm one of the primarily Mac-based developers of the FS2_Open engine. Hopefully I can assist, alongside the other suggestions here in the thread, to get your game working properly.

There's an issue with each of the Mac FS_Open 3.7.2 RC4 files at present. So best you either use an RC3 build for now, or wait for the download to be fixed.

Quote
also another thing I need to mention is that I get a black screen when I try to run a mod or just the regular FS2 that leads me to have to turn off my Mac.

There's a setting in the wxLauncher for "Run in windowed" mode. Whilst you are trying to debug this blackscreen issue, that should mean you don't have the restart your Mac.

A new copy of your fs2_open.log would be much appreciated as well.
« Last Edit: August 17, 2014, 12:20:51 am by Echelon9 »
 

Offline Silent Fox 104

  • 24
Re: 70 warnings when starting up a mod for freespace open
Reply #18 on: August 17, 2014, 12:58:24 am
Okay I have an update I no longer get a black screen, it seems that whatever mod or no mod is activated it starts up Blue planet 2 and this is with no mod selected. I was every able to play it actually but it's weird like I'm stuck in it. I took a few screenshots that have attached to this that might help along with my fs2_open.log.

[attachment kidnapped by pirates]
 

Offline niffiwan

  • 211
  • Eluder Class
Re: 70 warnings when starting up a mod for freespace open
Reply #19 on: August 17, 2014, 01:13:51 am
Can you post a screenshot of your launchers mod tab?
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...
Print
Pages: [1] 2 Next >   Go Up
« Previous Thread Next Thread »