Warping Cutscene Incorrect?

[Wolf]

I have KM 1.0 and Galaxy Charts installed, this problem occurred before GC was installed too.

Basically, in videos I of BC with either or both mods installed, it has the traditional warp sequence.  By traditional, I mean the cutscene is of the ship at a distance and then the ship flashes its warp engines before "stretching" as it goes to warp and then you get the flash in the far distance.

What is happening in my case is that it just runs the standard F9 initialised flyby cutscene, so it looks like it just goes to high sub-warp speeds (like when intercepting) and then it the flash occurs up close to the camera.

Why is mine install doing this?  How can I fix it?

Thanks.

[MLeo]

Play, if possible, with the various WarpFX settings (assuming you both have NanoFX and a NanoFX Config module installed).

[Wolf]

Disabling two of the settings now results in BC gives the black screen of doom.  This is my second install of it since I last played with any of the FX settings it caused it to go wrong.

Now it looks like I have to do it again, since I cannot do anything with it, not even get the logs viewable etc. 

[MLeo]

Disabling two of the settings now results in BC gives the black screen of doom.  This is my second install of it since I last played with any of the FX settings it caused it to go wrong.

Now it looks like I have to do it again, since I cannot do anything with it, not even get the logs viewable etc. 

The black screen isn't "death" or "doom" get us a console report and we'll see what we can do.

Now, mostlikely, you need to just delete your NanoFX config and you shall be on your way.
It's found in scripts/Custom/NanoFXv2/ you must delete the files NanoFX_Config.py and NanoFX_Config.pyc

[Wolf]

I have deleted those files and it still does not function now.

I have used the testmode extension in the shortcut, but both ` and ~ keys fail to do anything.  Hitting enter also fails to do anything.  The game continues to use very little in the form of resources when I check its activity on the task manager (Firefox uses more than the game does when this game isn't working!).

It appears it is an initiliasation problem.  Unfortunately it's difficult to get a report when the posted method appears to not work.  :o  Advice and guidance please.

EDIT:  Okay, I have copied the NanoFX from KM 1.0 and over-wrote the existing one in the Bridge Commander Script folder.  The game now functions.  So perhaps we can now get back to getting this warping effect sorted out.  :lol:

I do not know what settings to alter, since we have camera, warp and other settings that can be played with.  So a guide through what to alter to and what would be an ideal setting perhaps would be hugely appreciated! 

[MLeo]

Well, I'm afraid I can't help you with the settings, since that is a personal touch you want to apply.

If it happens again, please upload the config file (the .py version of one of the two files I mentioned before).

Also, about the -TestMode, make sure you put a space between STBC.exe and -TestMode (if it ends in a " then you need to put a space between that, so it becomes STBC.exe" -TestMode). And you _must_ spell it exactly (case and all) as -TestMode and you must start the game the game through the altered shortcut.
Further more, if you don't have an US keyboard (or US layout) then it might be another key, namely multiply (numpad or otherwise). Otherwise it's the "backquote" as it's also called.

[Picard_1]

MLeo,

There's a mutator in KM 1.0 for automatic test mode. That didn't work, so I created the manual shortcut.
test mode still doesn't work on my end.

[MLeo]

Download this:
http://bc-central.net/forums/index.php?action=dlattach;topic=2695.0;attach=12266
And place it in scripts/Tactical/

Now the problem can't lie with BC anymore, provided you push the right key and you installed it correctly.

It must be called __init__.py

[Picard_1]

Thank you, but it didn't work. When I push the `~ key, I get the box with a Kobayashi Maru
logo. It's transparent, not black like the default, and there's no command line.

[MLeo]

That's the console.


Press Enter, then Print Screen, then type in the following:

Code: [Select]

import sys
sys.exit()BC will now quit.
Open Paint, press Ctrl + v (paste). Save as png and upload here.

[Picard_1]

Yeah, I can get the console up like in BC 1.1, but the command line won't load.

Screen capture here: http://www.4shared.com/file/37380582/8c2aabb8/BC_Console.html?

[MLeo]

Try looking in scripts/Custom/ and see if you have any txt files there, if you have, zip them up (only the .txt files) and attach them here.

[Picard_1]

That's just the console dump and chat log...

http://www.4shared.com/file/37443249/784259ee/Textfiles.html

[MLeo]

That's just the console dump and chat log...

Isn't that not _exactly_ what we've been looking for?

Too bad this doesn't say much.
Any other logs you can see?

Also, if you have GravityFX installed, make sure you have a "Logs" directory in scripts\Custom\GravityFX\

[Picard_1]

Unfortunately, I don't have any other texts to provide you with.

This problem is bugging me because it doesn't occur with BC 1.0 or 1.1, only
KM 1.0.

Do you run automatic test mode in KM 1.0? Does it give you any trouble?

[Utenite]

I have KM 1.0 and Galaxy Charts installed, this problem occurred before GC was installed too.

Basically, in videos I of BC with either or both mods installed, it has the traditional warp sequence.  By traditional, I mean the cutscene is of the ship at a distance and then the ship flashes its warp engines before "stretching" as it goes to warp and then you get the flash in the far distance.

What is happening in my case is that it just runs the standard F9 initialised flyby cutscene, so it looks like it just goes to high sub-warp speeds (like when intercepting) and then it the flash occurs up close to the camera.

I don't know if this is relevant or not, but I started a similiar topic about GC changes to the NanoFX warping cut scene at BCS-TNG.

http://bcs-tng.com/forums/index.php?topic=1662.0

I don't run a KM install, but I can easily get the original NanoFX cut scene back if I disable the GC mutator.  I do prefer the NanoFX cut scene, but quickbattle simply is not the same without GC, so GC gets left on.

As mentioned by USS Frontier in the thread, the GC update patch will allow custom warp scenes, so I'm hoping someone with the scripting knowledge will change the warp cut scene back to the NanoFX version .