Topic: Hex Editing of Starfleet executables  (Read 185132 times)

0 Members and 1 Guest are viewing this topic.

Offline TAnimaL

  • Lt.
  • *
  • Posts: 771
  • Gender: Male
    • Combat Logs from the Cold Depths of Space
Re: Hex Editing of Starfleet executables
« Reply #400 on: November 06, 2015, 09:59:49 pm »
I started to giggle when I read your post Adam but realised you probably meant it in all seriousness.  :)

There are no pics of TR beams in action because there are no pics in SFB really. There is artwork on the covers, and in the "magazine" Captain's Log there are occasional images but no one (I know) takes these too seriously. I mean, over the years the artwork has ranged from crude sktechs to primitive computer-generated to more sophisticated art, so they're mostly filler. In fact, if I know SFB players, I'll bet there has been more than a few rules arguments that started over something in an image -  it doesn't take much to get a "rules lawyer" going.

I'm including a few pictures from covers with Andros, just to give you an idea what I'm talking about. I think your "TRs look like tractors" is as good as an approach as any. Whatever looks cool ;)

Offline TAnimaL

  • Lt.
  • *
  • Posts: 771
  • Gender: Male
    • Combat Logs from the Cold Depths of Space
Re: Hex Editing of Starfleet executables
« Reply #401 on: November 06, 2015, 10:03:08 pm »
And usually, it was just counters on a map, unless you had some miniatures around.  :laugh:

Offline Bernard Guignard

  • Cad Schematics are our Speciality
  • Lt.
  • *
  • Posts: 887
  • Gender: Male
  • Trek Canon!!! I NO believe in TreK Canon!!!.
Re: Hex Editing of Starfleet executables
« Reply #402 on: November 07, 2015, 06:54:19 am »
Damn Seeing those SFB pictures of the minis are bring back memories  ;D

Offline TAnimaL

  • Lt.
  • *
  • Posts: 771
  • Gender: Male
    • Combat Logs from the Cold Depths of Space
Re: Hex Editing of Starfleet executables
« Reply #403 on: November 07, 2015, 01:01:36 pm »
As promised/threatened, here are the offsets I have found for the OP exe. This is not complete but I'd rather not hold back posting this any longer. As I note in the readme, some things are handled differently in OP than they are in CE. For example, I couldn't find plasma-degradation values; you can assign ranges based on type however. And special shuttles (WW, scatterpacks, suicide, Assault) all use the same speed controller, unlike separately as in CE.

Here are CE elements I couldn't find in OP:
  • Capture enabling (might not exist in OP?)
  • Mines detonation, activation ranges (I haven't tested all of the possibilities yet)
  • Max Range limiters on Phasers 1/2/3/4 (might not exist in OP?)
  • Point Defense controls - beyond my limited abilities, might be handled differently in OP
  • Photon holding as multiple of charge rate (I haven't tested all of the possibilities yet)


Here are CE elements I didn't look for yet in OP
  • Fusion (std, OL,SOL) charge rate, total charge
  • Hellbore charge rates
  • Missile endurances
  • PPD hold costs, OL max range limiter
  • Tractor engagement range

I also found some interesting things about the TR Beams and the not-as-broken DroD & DroE but I'll maybe start another thread for that.

The attachment "OP_EXE_Offsets.ZIP" is just the offsets. The attachment "SFCOP_Exe_Editing.zip" contains the SFC_Editor1.3.3 program, the offsets and the .bat to load them, but you'll need to place a copy of the StarFleetOP.exe into that folder. Again, thanks to everyone else on this thread for getting it this far

EDIT: small issue found in the offsets, newer versions below
« Last Edit: November 07, 2015, 05:40:52 pm by TAnimaL »

Offline TAnimaL

  • Lt.
  • *
  • Posts: 771
  • Gender: Male
    • Combat Logs from the Cold Depths of Space
Re: Hex Editing of Starfleet executables
« Reply #404 on: November 07, 2015, 01:09:47 pm »
I also did a little tweaking to the stock OP exe and placed it in the Library, called "OP_exe_SFB_Normals"


ftp://www.dynaverse.net/sfc2_op/Uploads/OP_Exe_SFB_normals.ZIP

In this exe, I changed anything I found in the stock OP exe back to "SFB standards"

-TR beams used different range bracket values in stock OP than they do in SFB. Fixed to SFB brackets (0-3, 4-5, 6-8, 9-12, 12-18 19-26)
-Proximity Photons changed back to SFB charts to stop the complaining
-Plasma speeds changed back to 32 (except Plasma-X, still 40), same as missiles. You're welcome.
-All "light" weapons for fighter (Disruptors, photons, fusions, Hellbores) changed back to standard damage, not half

This is just meant as an experiment I wanted to play around with. Please please let's not start any sort of digression about "magic" anythings. ::)

Offline TarMinyatur

  • Lt.
  • *
  • Posts: 938
  • Gender: Male
Re: Hex Editing of Starfleet executables
« Reply #405 on: November 07, 2015, 03:21:40 pm »
Thanks for your efforts, TAnimaL.

Looks like there is an address error for the OL Fusion Beam table as viewed in the SFC_Editor. The quicktip info looks good, but the 6x6b chart isn't quite right. It has two columns full of zeroes. All the other charts look good.

I'd fix this myself, but I've forgotten how to do it. It may take me a few days to relearn this stuff.

Offline TAnimaL

  • Lt.
  • *
  • Posts: 771
  • Gender: Male
    • Combat Logs from the Cold Depths of Space
Re: Hex Editing of Starfleet executables
« Reply #406 on: November 07, 2015, 05:38:33 pm »
Thanks for the catch Tar, I found that error and fixed it, attaching new versions.

Adam, I didn't see anything in your previous notes re: point defense enable/disable, maybe this is something  easier to find in IDA? In HxD it would be impossible to discern one option point byte from another. There was one mention in your notes about P3 range lmitations but I didn't really get it, and I guess I don't really see range limitations as that important. Point defense would be nice tho.

(And if it was somewhere else in this thread, sorry, I must have missed it.  Getting close to 33 pages now!)

Offline TarMinyatur

  • Lt.
  • *
  • Posts: 938
  • Gender: Male
Re: Hex Editing of Starfleet executables
« Reply #407 on: November 08, 2015, 01:56:13 pm »
TAnimaL,

From your OP offsets.txt: "397688: 1d // Cloak range x10, added to true range // 60.0"

I don't think this offset is correct. SFC:OP should have a 50.0d modifier. The 60.0d modifier in CE's offsets is used to strengthen Community Edition's weak cloak. I could be wrong, but OP's cloak does not need a +6 range adjustment, on top of the doubled-range effect, which then gets passed to the Misery Chart (which CE lacks).

I'm looking for a 50.0d (double-precision float) value...

I found it.  .text:00438522 sub_438522

All seems ok. Cloak effect is range +1, +2, +3, +4, +5, and then range*2 +5.
Decloak is the reverse.
« Last Edit: November 11, 2015, 06:48:43 pm by TarMinyatur »

Offline Corbomite

  • Commander
  • *
  • Posts: 2939
Re: Hex Editing of Starfleet executables
« Reply #408 on: November 09, 2015, 08:23:54 pm »
Tar

I know by reading a previous thread of mine circa 2003 you stated the Stealth (+ECM) in the shiplist didn't work on EAW, but does it work in OP?

Adam


No.

Offline TarMinyatur

  • Lt.
  • *
  • Posts: 938
  • Gender: Male
Re: Hex Editing of Starfleet executables
« Reply #409 on: November 10, 2015, 06:04:00 pm »
Adam, somewhere there may be a variable's value (0 or 1) that defines an empire as fighter-equipped or PF-equipped. There probably is no value (such as 2, an arbitrary enumeration) that would allow a race to carry both types of attrition units. But Taldren might possibly have coded this capability very early on, before the segregation took place. If so, it would be easy to hex-edit. But not so easy to locate.

Rod O'neal's manipulation of the shiplist may be the most practical way to get a pair of PFs on a Klingon D7C.

Offline [UFP]Exeter

  • SFC4 Dev
  • Lt. Commander
  • *
  • Posts: 1080
  • SFC4 Lead Developer
Re: Hex Editing of Starfleet executables
« Reply #410 on: November 10, 2015, 06:06:20 pm »
what is a pf?

Offline [UFP]Exeter

  • SFC4 Dev
  • Lt. Commander
  • *
  • Posts: 1080
  • SFC4 Lead Developer
Re: Hex Editing of Starfleet executables
« Reply #411 on: November 10, 2015, 06:13:35 pm »
fast,
turns sharp,
decent offense,
no defense.


a glass cannon

Offline Corbomite

  • Commander
  • *
  • Posts: 2939
Re: Hex Editing of Starfleet executables
« Reply #412 on: November 10, 2015, 07:21:02 pm »
what is a pf?

Pseudo Fighter, Like a TNG/DS9 Runabout, Almost a mini, tiny, limited Frigate, Fast Patrol, Corvette like
Whereas a standard fighter is like the fighters seen in DS9, no shields

Hope that description helps

Adam


PF stands for Fast Patrol ship, not Pseudo Fighter. Pseudo Fighter is more of a nickname.


fast,
turns sharp,
decent offense,
no defense.


a glass cannon


Sure, one is, but you usually had twelve or more on the board in a decent sized battle involving them. And they were hard to knock off if used correctly.

Offline Corbomite

  • Commander
  • *
  • Posts: 2939
Re: Hex Editing of Starfleet executables
« Reply #413 on: November 10, 2015, 07:35:47 pm »
Adam,

Remember that the donor ships for the Romulan carriers will not get a NSM. It's part of that hard coding I mentioned before.

Offline Corbomite

  • Commander
  • *
  • Posts: 2939
Re: Hex Editing of Starfleet executables
« Reply #414 on: November 10, 2015, 08:10:47 pm »
With good reason. Only pirates get engine doubling. It would carry over to the transplant race for the same reason only Romulan ships originating in the Romulan part of the shiplist get a NSM.

Offline [UFP]Exeter

  • SFC4 Dev
  • Lt. Commander
  • *
  • Posts: 1080
  • SFC4 Lead Developer
Re: Hex Editing of Starfleet executables
« Reply #415 on: November 10, 2015, 08:12:55 pm »
NSM?

Offline Corbomite

  • Commander
  • *
  • Posts: 2939
Re: Hex Editing of Starfleet executables
« Reply #416 on: November 10, 2015, 08:58:51 pm »
That reminds me; someone has to bump NSM back up to 50 pts where they belong. Whomever dropped them to 35 was just a hater  :P.

Offline TarMinyatur

  • Lt.
  • *
  • Posts: 938
  • Gender: Male
Re: Hex Editing of Starfleet executables
« Reply #417 on: November 10, 2015, 09:42:23 pm »
No consistency on Taldren's part...

Suicide shuttles do 25, instead of a max of 18, but they consume a t-bomb.
NSMs do 50? Is that right? I never deployed one in SFB. NSMs should only be on old-school Romulan ships, like the BH, WE, and KE. It seems wrong for a K5R or a KRC to have one of these suckers for a huge self-destruction blast.

Offline Corbomite

  • Commander
  • *
  • Posts: 2939
Re: Hex Editing of Starfleet executables
« Reply #418 on: November 10, 2015, 10:28:10 pm »
NSM did 50 in SFC1. I was just waxing nostalgic about how much more satisfying the "Nuclear Space Mine Detonated!" message was then. They do 35 in SFB and old Rom hulls get them for free and pretty much any Rom hull can get them as optional equipment, which Taldren just ignored in favor of all ships just getting one if you want it. With the weaker cloak and double internals I agree with that free option (and the 50 pts!).


Offline Corbomite

  • Commander
  • *
  • Posts: 2939
Re: Hex Editing of Starfleet executables
« Reply #419 on: November 10, 2015, 10:38:11 pm »
You know, I just realized that we could have had minelayers with captor mines and TBomb/dropped small mines the whole time.  ::)