$Created: 02/20/09 at 15:14:46
$Modified: 01/04/19 at 14:31:34
I tried to activate it and got this error*snip*
There are some... erratic ship movements,
Well, vasudan destroyer changes its direction few times during second mission. Maybe (and probably) it has a purpose, but looks a bit funny to me (maybe just my twisted mind finds it funny)
And also it is possible to destroy Ravanas main beams in first missions - damage made to the hull stays, but beams regenerate.
The campaign is setup pretty much specifically for trebs and maxims which are required to do all the beam disarming at once, meaning all other loadout options are basically traps.
But then the mission red-alerts into kind of a cluster **** of the shivans throwing all the things at you at once
[...] with no way to repair [...] and more leeway in terms of repair
But this is also not actually communicated to you in the briefing itself
Typhon with the funny vasudan name
I tried to activate it and got this error*snip*
Knossos or Manual?
If Knossos please check which build you are launching (under FSO Setting, either via the Mod itself or your global settings), this error is associated with Axem's Mark Box-Script, which requires a 3.8.1 build to run.
If Manual, same applies - there is a link for build I used in testing this week.
I tried it again on manual with the January 9, 2019 nightly and I was able to start the campaign but there were a number of graphics errors. There were no grid lines in mission briefings and in the actual mission there were no actual ships, only a few glowing dots that formed an outline of ships.
I tried it again on manual with the January 9, 2019 nightly and I was able to start the campaign but there were a number of graphics errors. There were no grid lines in mission briefings and in the actual mission there were no actual ships, only a few glowing dots that formed an outline of ships.
Sorry for the long delay ... I am currently occupied with important RL stuff...
Anyway, please provide a fs2_open.log (http://www.hard-light.net/forums/index.php/topic,56279.msg1180359.html#msg1180359).
Nothing of what you have described seems to be my fault, but with a fs2_open.log there is better chance of finding out what is happening.