KM 1.0 Exit Warp

[Picard_1]

The original WarpFX.py was modified by USS Sovereign, here's an excerpt taken
from the modified script.The script in red indicates he has "tweaked something
in NanoFX:

Modified by USS Sovereign                                                                                                                         
      Consider this something that should have been done in BC from the   
      beginning. Again I've removed my idiotic bable from the old version.   
      I've modified the way how calculating warp time works, needed for the 
      tweak I've made in NanoFX. I also needed to modify this file to return
      warp time in order to determine warp degradation.

Maybe this tweak caused the camera to be stuck in position since altering python
can have strange results. Perhaps undoing the tweak may correct the issue.

[Mario]

Did you actually read what the desc I left behind said?

It returns values to the CWS to determine the warp degradation that's all!

Code: [Select]

        ### No decimals, only clean numbers
        iTimeToWarp = round(iTimeToWarp)
        global WarpTime
        WarpTime = iTimeToWarp

Code: [Select]

##### Sov Edit
def ReturnWarpTime():
    global WarpTime
    return WarpTime
Remove it if you want thus you'll basically kill the CWS mod if you want, though it will NOT fix anything but will cause a bunch of errors when you warp.

I don't leave descriptions in the files I modify for nothing you know.

[Picard_1]

Remove it if you want thus you'll basically kill the CWS mod if you want, though it will NOT fix anything but will cause a bunch of errors when you warp.

Relax. Why would I want to disable CWS? The scripts don't make much sense to me;I am just trying to find a solution to the problem. Maybe you can help.

[Mario]

Relax. Why would I want to disable CWS?

I have no idea, but by removing those lines you are crippling your installation. I am just stating that. Before you come back saying that your installation is screwed up after you undo the changes I made to the file.

The scripts don't make much sense to me

That's why you have the description of the modifications I made to the file, which you also posted but failed to understand.
What you are suggesting is basically like operating a patients heart who suffers a mild cold only, not very helpful or a good move.

Maybe you can help.

No, I can't. Few reasons:
- I didn't write this particular code
- I'm not familiar with the KM's new code also
- I'm not much familiar with Defiants changes
- I don't have KM installed
- I'm too busy with personal matters at the moment

[Picard_1]

That's fine if you're to busy to help. Frankly, I feel like your responses were a bit rude when you said,

That's why you have the description of the modifications I made to the file, which you also posted but failed to understand.

Ok, so I don't know scripting. Am I supposed to? I am also busy with work and I don't have time to spend learning python script. It would be great to know it for BC, but it's not necessary for me to know outside the game.
 
What you are suggesting is basically like operating a patients heart who suffers a mild cold only, not very helpful or a good move.

You may not have liked my suggestion, but myself and others have been looking for a way to fix the problem. It doesn't feel nice when
someone tells you "not very helpful or a good move." If you don't like what I say, don't say anything. At least find a more reasonable answer. We are part of a community designed to help solve issues for BC, not create them.

[El]

Knock it off please guys.

[Mario]

lol

Is this how your problem looks like?

1st clip when the camera doesn't track the ship at all
2nd clip is the normal one (non KM installation)

This is the same set and the same installation only...

[MLeo]

TBH, (I just noticed this), this "problem" has happend to me to any version of NanoFXv2Beta, mostly for large ships such as the Galaxy.

[Mario]

This "problem" isn't a problem at all but the system script is actually missing an important line. I've found that out when I was making slipstream.

This happens only in systems which do not have a "Player Start" waypoint in the system file. If you were to check the slipstream code you'll notice it's designed to use the "Player Start" navpoint also and will make a compensation for sets which do not have a "Player Start" Location.

So, all you need is something like this in the system file (usually scripts\systems\myset\myset.py):

Code: [Select]

# Position "Player Start"
kThis = App.Waypoint_Create("Player Start", sSetName, None)
kThis.SetStatic(1)
kThis.SetNavPoint(0)
kThis.SetTranslateXYZ(-3.792000, 0.000000, 0.000000)
kForward = App.TGPoint3()
kForward.SetXYZ(0.417716, 0.620277, 0.663905)
kUp = App.TGPoint3()
kUp.SetXYZ(-0.898685, 0.389602, 0.201435)
kThis.AlignToVectors(kForward, kUp)
kThis.SetSpeed(25.000000)
kThis.Update(0)
kThis = None
# End position "Player Start
Even some stock systems are missing this. This "problem" has been around since the start of BC.

[Picard_1]

The first clip shows exactly what happens when you exit warp. The player start lines
are also in mysystem.py

[Mario]

Not likely. Check all systems and their respective files. The ones which do not have "Player Start" won't work correctly.

[milenent]

So how do we repair it because I didn't understand at all.

[KrrKs]

So, all you need is something like this in the system file (usually scripts\systems\myset\myset.py):

Code: [Select]

# Position "Player Start"
kThis = App.Waypoint_Create("Player Start", sSetName, None)
kThis.SetStatic(1)
kThis.SetNavPoint(0)
kThis.SetTranslateXYZ(-3.792000, 0.000000, 0.000000)
kForward = App.TGPoint3()
kForward.SetXYZ(0.417716, 0.620277, 0.663905)
kUp = App.TGPoint3()
kUp.SetXYZ(-0.898685, 0.389602, 0.201435)
kThis.AlignToVectors(kForward, kUp)
kThis.SetSpeed(25.000000)
kThis.Update(0)
kThis = None
# End position "Player Start