Ships spawn in with chain drives active when previously not

[spocklin]

All of my ships were saved with their chain drives inactive and now instead spawn in and jump away. This is not a case of me forgetting to turn them off or me having a bad logic loop it is just spawning in and jumping away without ever being previously activated. This started occurring only after the asteroid update had happened.

 

[TwoNiner]

You're the only one having this problem so it must be a faulty logic loop

 

[spocklin]

Other users have reported this to me as well. I have tested this with multiple other user's chain drive systems as well. You also completely missed what I said apparently. You jumped to a conclusion to quickly before actually digesting what I said. I said that before this previous update my ships spawned in without having the chain drive activated and now they spawn in with it activated and jump away from me. This is coming from the same blueprints I have been spawning in and now they have this problem after this big update and they have had nothing changed on them so I don't see how it could have been my fault given this evidence.

 

[Valck]

Are those drives being clocked by a logic or a rail clock?

 

[TwoNiner]

Other users have reported this to me as well. I have tested this with multiple other user's chain drive systems as well. You also completely missed what I said apparently. You jumped to a conclusion to quickly before actually digesting what I said. I said that before this previous update my ships spawned in without having the chain drive activated and now they spawn in with it activated and jump away from me. This is coming from the same blueprints I have been spawning in and now they have this problem after this big update and they have had nothing changed on them so I don't see how it could have been my fault given this evidence.

I took the liberty of spawning in your BP on NFDbuild to test this out. Yes it jumps away. I caught it to see that the chai drive was infact saved when active. This was due to it having a shité logic clock. Maybe u should build better logic circuits.

 

[Heillos]

I think seeing a blueprint of the chaindrive which is facing this issue would help greatly (and, if you would claim that it requires secrecy, my counterpoint is that the technology has plateaued almost entirely, and it's unlikely that you're onto anything groundbreaking). It's difficult to diagnose why this issue might be occurring without understanding the logic setup involved. Furthermore, more clients testing it would lend weight to the claim that there is something incorrect occurring, rather than simple user error.

 

[spocklin]

Yeah I don't build ships with chain drives period because they are too vulnerable to inhibitors. The ones I have are ones that I bought from many other users. These were spawned in without a problem before this update and are now broken. They should not be spawning in with the drive on period as they were not turned on when I got them or saved them.
[DOUBLEPOST=1466743655,1466743581][/DOUBLEPOST]

I took the liberty of spawning in your BP on NFDbuild to test this out. Yes it jumps away. I caught it to see that the chai drive was infact saved when active. This was due to it having a shité logic clock. Maybe u should build better logic circuits.

Maybe you shouldn't harass other users on their support threads when they have a concern. I am in no way trying to start a flame war but I will not tolerate someone who is blatantly using my threads to start such a flame war.

 

[TwoNiner]

Let me walk you through a potential solution:

1 spawn in the ship
2 use Tab+f8 to get into the ship
3 turn off the chain drive
4 save the BP again
[DOUBLEPOST=1466743758,1466743681][/DOUBLEPOST]Just seems like a stupid support ticket to me

 

[DrTarDIS]

show the bp. if it's the kindthat "charges automaticly while docked" do not save it if it is docked: this saves it in "on" state.

 

[StormWing0]

This is where docking it to a tiny docking ship comes in handy. Can't jump if docked. That said states like this need to be saved and loaded correctly.

 

[spocklin]

Let me walk you through a potential solution:

1 spawn in the ship
2 use Tab+f8 to get into the ship
3 turn off the chain drive
4 save the BP again
[DOUBLEPOST=1466743758,1466743681][/DOUBLEPOST]Just seems like a stupid support ticket to me

Tab+F8 only works if you are an admin.

 

[Ezekial Alexander]

Tab+F8 only works if you are an admin.

You have the BP. Launch a single player and just admin fix it

 

[Heillos]

spocklin you've yet to provide anything more than anecdotal evidence of you having this issue. TwoNiner contends (also anecdotally, mind) that you are mistaken and the chaindrive was saved while on. Again I must ask that you provide a blueprint, any blueprint, which exhibits this behavior (and it can be proven that the blueprint does this even when certainly saved while off), so that others may verify your claims. Without such evidence, I don't see this thread going anywhere meaningful.

 

[spocklin]

mod please lock

 

[Groovrider]

Just saying from experience: Certain logic arrangements can hit an active state while being partially loaded in an unloaded sector. Been there done that. Solution: Add a failsafe that deactivates the clock while undocked and another manual cutoff for the whole system.

 

[Zerefette]

You could use a jump inhibitor.