HLP Network

News:

Thanks to the hard work of rev_posix and Sandwich, the HLP email system has been fixed!  All registration emails from the past few months have been re-sent.  If you still need help, please sign on to Discord and let us know.  The Discord link can be found in the top navbar under the HLP menu. ヾ(´︶`♡)ﾉ

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

Author Topic: Getting Errors while trying to start a mod  (Read 1206 times)

0 Members and 1 Guest are viewing this topic.

Offline Drageno

  • 21
Getting Errors while trying to start a mod
on: April 01, 2015, 11:20:36 am
Good evening guys!

I hate it that my first post on here is about having a problem, but i have searched this forum for my problem
and haven't found any solution to it, so it cant be helped.

So the problem is the following:
When i first tried to start Silent Thread reborn i got this error message below and was at first thinking that it
was a mod specific problem and intended to play another mod and got the same error. I tested a bunch of other
mods and got the the same problem. The 2014 mediavps for FSport and FS2open are also affected. The 3.6.12 versions
are running though.
I installed the mods and FSOpen with the Installer just a few days ago and haven't
altered any files so i dont really know whats wrong here. I hope that maybe one of you folks can help me :s

System Specs:
Win7 64bit
intel i7-2600 3,4 Ghz
8gb RAM
GTX 550 TI

Quote
mv_effects-sdf.tbm(line 16:
Error: Required token = [#END] or [$Species_Name:], found [$Countermeasure Type:   Type One] .

ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_12r_INF.exe! <no symbol>
fs2_open_3_6_12r_INF.exe! <no symbol>
fs2_open_3_6_12r_INF.exe! <no symbol>
<no module>! <no symbol>
<no module>! <no symbol>
<no module>! <no symbol>
<no module>! <no symbol>
<no module>! <no symbol>
<no module>! <no symbol>
<no module>! <no symbol>
fs2_open_3_6_12r_INF.exe! <no symbol>
<no module>! <no symbol>
<no module>! <no symbol>
<no module>! <no symbol>
 

Offline Macfie

  • 210
  • If somebody made a campaign I've probably got it
Re: Getting Errors while trying to start a mod
Reply #1 on: April 01, 2015, 11:38:50 am
You are using an out of date FSO exe.  You need to use a newer FSO exe file if you are using the 2014 media VPs.  I would recommend 3.7.2 RC5.
Normal people believe that if it isn't broke, don't fix it. Engineers believe that if it isn't broke, it doesn't have enough features yet.
The difference between Mechanical Engineers and Civil Engineers is:
Mechanical Engineers build weapons.  Civil Engineers build targets
An optimist sees the glass half full; the pessimist sees it half empty. An engineer sees that the glass is twice as big as it needs to be.
 

Offline Drageno

  • 21
Re: Getting Errors while trying to start a mod
Reply #2 on: April 01, 2015, 11:46:56 am
I have such an .exe-file in the folder. hmm should is just remove the 3.6.12 exe then? I remember i had installed FSO previously maybe thats an leftover
 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: Getting Errors while trying to start a mod
Reply #3 on: April 01, 2015, 11:56:58 am
Quote from: Drageno on April 01, 2015, 11:46:56 am
I have such an .exe-file in the folder. hmm should is just remove the 3.6.12 exe then? I remember i had installed FSO previously maybe thats an leftover
There should be no reason to keep such an old executable around, so it should be safe to delete.
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 Drageno

  • 21
Re: Getting Errors while trying to start a mod
Reply #4 on: April 01, 2015, 12:10:25 pm
Ok that worked and i figured out that i can select the .exe that shall be used in the launcher x)
Just learned something new about the launcher x)

Thx for your help though guys. Everything seems to be working now :)
Print
Pages: [1]   Go Up
« Previous Thread Next Thread »