[jdh300x]

When i try to open up a mod. Any mod part of fs2 inf 3.6.12 including the media vp's, i get this error code, or something like it.


bp20wep.tbm(line 979:
Error:Missing required token: [=Count]. Found [type:   Ring]
in weapon: ShockwaveEffect
instead.

ntdll.dll! ZwWaitForSingleObject = 21 bytes
kernel32.dll! WaitForSingleObjectEx = 67 bytes
kernel32.dll! WaitForSingleObject = 18 bytes
fred2_open_3_6_12r_INF.exe! <no symbol>
fred2_open_3_6_12r_INF.exe! <no symbol>

That is when i try to open Blue Planet 2.
I have the same kind of problem for all the other mods.
The only way i can play is by pressing "no mod"
I have already tried running the installer again twice, and it has done nothing to help.

I need a fix.
Thankyou
Jdh300x

[niffiwan]

Can you please post your fs2_open.log?  Check the link in my sig for details.

[The E]

BP2 is NOT compatible to 3.6.12, and needs a 3.6.14 build in order to run.

[jdh300x]

How can i get the 3.6.14 build. I tried the open installer.
And how do i post the freespace log?

[MatthTheGeek]

God damnit.

INSTALLER = EVIL

How people still manage to dig up that outdated and currently non-functional piece of software after we removed all the links to it is beyond me.


You can find .14 RC builds in their stickied release thread.

How to post a debug log here.

[jdh300x]

Installing the new build fixed it.
Thankyou all.

[Goober5000]

FYI, 3.6.12 is still the latest official build.  It's not surprising that that's what he was trying.

[MatthTheGeek]

He was using .12 because that's what the installer gives him, not because he knew this was the latest stable build.

Blue Planet release thread clearly indicates .12 won't work. If he had installed manually instead of using the installer, we wouldn't be having this conversation. Hence the thread I started in Support.

[headdie]

Yet the standing recommendation is to build mods to the current stable build which is 3.6.12.  RCs are not stable builds, they are the attempts by SCP to build a stable version of the trunk build ready for release as a stable build but they are still likely to contain error, heck look at RC5 or the fact we are on RC7 for proof, as such RC builds are not stable builds and the argument here if any is that BP should have waited for SCP to release 3.6.14 stable!

Personally I am glad they didn't wait but that is another matter.

[The E]

Sure, we could have waited.

But then, noone knew that .14 would take more than half a year to get finished.

[headdie]

As I say I am glad you didnt wait but until 3.6.14 stable is released threads like this are to be expected due to 3.6.12 being the current stable version and not entirely the posters fault as the fact the player is using to their knowledge the latest release/stable/user friendly version of the exe. 

Yes they should read the requirements in full but it is like someone installing a game on their top spec computer with latest updated drivers and it dont work, then after posting on a forum about their issue they get told that it's because they are not using the public beta drivers for their NVidia/ATI which the coder is using for a feature created in that development cycle.

[jr2]

Can we make the correct RC build part of the BP install in the Installer?

[mjn.mixael]

Can we make the correct RC build part of the BP install in the Installer?

That only solves the symptoms.. we need to cure the cause. In this case, finish 3.6.14 someday.

[jr2]

Yes, but meantime, for the sake of the end user, the dirty hack needs to be in place.  jdh300x posted.  How many didn't?

[Droid803]

I thought the only thing keeping 3.6.14 in RC was the HeadAni stuttering bug.
Which is now fixed...

[headdie]

I thought the only thing keeping 3.6.14 in RC was the HeadAni stuttering bug.
Which is now fixed...

not sure but even in that case the SCP team still need to officially release the stable build for the situation to be resolved

[Goober5000]

Yes, but meantime, for the sake of the end user, the dirty hack needs to be in place.  jdh300x posted.  How many didn't?

The only reason the installer is configured to download 3.6.12 is because 3.6.12 is the official build.  I could change that right now (all I need to do is modify a text file on the website) but that would mean anyone who uses the installer would be getting an unofficial build.  That would open up a new can of worms such as the head.ani stuttering bug and the confusion between a RC and a final build.  So it's really a question of which can of worms you prefer.  And keep in mind that the vast majority of campaigns don't require 3.6.14.

I thought the only thing keeping 3.6.14 in RC was the HeadAni stuttering bug.
Which is now fixed...

Yup.  But now we need to bring the backports up to date.  And there are two small issues that popped up since the head ani bug was reported.