Move deflection

[hsnewman]

I'm having a problem with 2.2, although the documentation says "If the computer is inoperative, navigation during warp and impulse movement becomes inexact.", I can't seem to replicate the behavior. Anyone have any ideas why this is the case?
Here is an example of the 2.3 test I did:
Damage Report for Savannah

Device Damage

Deflector Shields 430.0 units
Warp Engines 162.9 units
Impulse Engines 236.6 units
Life Support 596.5 units
Torpedo Tubes 578.4 units
Phasers 415.3 units
Computer 301.4 units
Radio 610.9 units
Tractor Beam 567.9 units

2LSD> st

Stardate 4
Condition Red
Location 24-54 <===
Torpedoes 8
Energy left 3576.0
Damage 2025.4
Shields -100.0% 2500.0 units
Radio damaged

2LSD> mo 3 3 <===

1LSD> st

Stardate 5
Condition Green
Location 27-57 <===
Torpedoes 8
Energy left 3540.0
Damage 2025.4
Shields -100.0% 2500.0 units
Radio damaged

and for 2.2:
4LS> da/st

Device Damage

Shields 161.0
Warp 120.6
Impulse 288.9
Life Sup 319.4
Torps 134.8
Phasers 61.0
Computer 348.1
Radio 5.1
Tractor 56.1

4LS>

SDate 6
Cond Green
Loc 40-16 <===
Torps 5
Ener 4878.0
Dam 826.2
Shlds -100.0% 2500.0 units
Radio On

4LS> mo -3 -3 <===

S> st

SDate 7
Cond Green
Loc 37-13 <===
Torps 5
Ener 4842.0
Dam 826.2
Shlds -100.0% 2500.0 units
Radio On

[drforbin]

I think it's BS. You just can't use the computer navigation

[hsnewman]

Well, the help says it and in the move.for:
if (shpdam(who,KDCOMP) .ge. KCRIT) d = (ran(0) - 0.5) / 2.0 !add deflection if computer damaged

but doesn't seem to be doing anything to the move when the computer is > kcrit (300)...

[statespacedev]

hi harris please def keep us updated on all the stuff you find out while playing the 2.2 exe - to me it's really great someone is methodically doing that - wish i could as well but hasn't happened so far hahaha - what i remember is that the 2.2 exe crashed pretty soon, say after like five ten minutes? just curious, what's you're experience with it harris? do you get a lot of gameplay time in it? does it crash on you?

[hsnewman]

Well I haven't been stressing it like you do with robots :)
I have it up in a terminal for about a week or so, just using to test. It never has crashed for me.
It might be something to do with the version I have.
I'm using: https://archive.org/details/simh.pixel9.tar_202507
There are simh disks in that file which you can run: pdp10 startit (the files are in the tops-10 directory)
You might try those disks and see if they crash.
HN

[statespacedev]

ok good to know! thanks for that tar file harris will make a special effort to try that tar as a 'standalone self contained unit'! would be super useful to have a reliable real 2.2 for 'baseline reference'

[hsnewman]

I forgot to mention that those disks have both [1,2]decwar.exe (v 2.2) and [5,30]decwar.exe (v2.3) on them.
HN

[statespacedev]

was able to do 'r [42,42]decwar.exe' with those disks, as described at the link above (after doing make pdp10 to compile for raspi) - that decwar starts fine and says it's 2.3
hmmm, not able to do 'r [1,2]decwar.exe' though?
getting '?DECWAR.EXE not found'

[hsnewman]

After more testing, I had an instance of inaccuracy, I think it may only occur a % of the time:
LS> mo 3 3/st
@ @53-20 +2,-2 172.2 unit P V @51-22, -100.0%; Computer dam 164.9

2LS>

SDate 8
Cond Red
Loc 51-22
Torps 9
Ener 3566.6
Dam 1726.1
Shlds -100.0% 2500.0 units
Radio On

2LS> $ <=esc pressed

S>

SDate 9
Cond Green
Loc 54-26 <=not 3,3!!
Torps 9
Ener 3530.6
Dam 1726.1
Shlds -100.0% 2500.0 units
Radio On

[hsnewman]

I'm wrong they both are 2.3

…

On Fri, Oct 10, 2025 at 3:47 PM Noah Smith ***@***.***> wrote: was able to do 'r [42,42]decwar.exe' with those disks, as described at the link above (after doing make pdp10 to compile for raspi) - that decwar starts fine and says it's 2.3 hmmm, not able to do 'r [1,2]decwar.exe' though? getting '?DECWAR.EXE not found' — Reply to this email directly, view it on GitHub <#52 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMRQA3DUPKM4IQYCZ6KFDL3XAZQHAVCNFSM6AAAAACI3SPXUSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINRVGE2DQNQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[statespacedev]

ok thanks for confirming that harris - am all about the '2.2' hahaha:)