Star Trek UI (Demo Version)

[General Woundwort]

A mod that reworks the UI to look like STNG control panels, and some cool Trek sounds to accompany the change.

LOCATION: Shrapnel's upload program has gone totally haywire, so as an interim measure I have posted the mod on my Spaceports site (I apologise in advance for the barrage of pop-up ads you must endure - direct downloads aren't permitted w/o visiting the site ). Look for the link right below the link for my SEIV mod.

http://galileo.spaceports.com/~woundwrt/Mod.html

INSTRUCTIONS: Put the Zip file in your Starfury Demo folder, and unzip. It will overwrite most of the UI graphics and some of the sounds, so if you have a great attachment to the originals, make a copy of them first and save them elsewhere.

Please post any questions, comments, or suggestions here, so I can update the mod.

BTW, the full game disc arrived in the mail today.

[ October 06, 2003, 22:23: Message edited by: General Woundwort ]

[Tiwaking]

I know this post is old and everything, but that link appears long dead. The post sounds really promising so does anyone have a link to the Star Trek UI or *A* Star Trek UI?

[bearclaw]

I must have missed this one originally. Any ideas of doing a Star Wars UI?

[Tiwaking]

bearclaw said:
I must have missed this one originally. Any ideas of doing a Star Wars UI?

If you mean me: Yes and No. Im trying to make a Star Trek: Romulan mod, but I cant get the game to boot past the 'Select your ship' bit. A little backstory may be in order:

Last year I finally got around to doing something I've been meaning to do for AGES: Record a game of Space Empires III on paper(I dont like SE IV that much). Since I play with a set of Star Trek Tech which I modded in, it makes the game alot more fun and interesting.

Then I found out and bought Starfury, which is an incredibly easy game to moddify, just like SE III! Or so I thought.

I've been trying for 3 weeks to get my SE III game turned into a Starfury Campaign. I finally thought I'd ironed out all the bugs, but there's just one thing I cant get past:

Access violation at address 004C7BB0 in module 'starfury.exe'. Read of address 0000000C

Occurs when selecting "Romulan Fighter" in the starting ship screen. You can download what I have done for the Mod here Starfury Mod: Tiwas Romulan Panasa Campaign. The tonnages are based on Deciphers Star Trek: RPG

Notes: For starters the Campaign Map contains one system(Panasa) with no warp points. Only enemies are meant to be Panasan Fighters. Only ship you can use a Romulan Fighter. Both fighters use the Human Fighter model til I can get the game going properly. And yes, there IS a D'deridex model just WAITING for me to get my mod off the ground!

[Suicide Junkie]

Odds are good that the problem is something simple.
I'll take a look for ya.

[Suicide Junkie]

Well, I can't seem to figure out the cause of the crash, and the debug logs aren't showing anything out of the ordinary.

What things did you change since the last time it worked?


Some other problem areas I noticed during my search:
- Your slot layout for the Fighter is messy and overlapping. Lots of slots crammed on top of each other. Use my SFSlotmodder to help.
- Your heavy weapon slot has the same name as your light weapon slot (#1). This is bound to cause some confusion in the default component placement routine.
- Your fighter hull has a base crew of zero.
- Your fighter hull has a base energy storage of zero.
(These two may cause issues with the bar graphs, or instant death when trying to upgrade your cockpit)
- Your use of the prevents crew death ability indicates you don't quite understand how it works:
"Base Crew Death Rate Per Second" on the hull specifies how fast your crew decreases when you have NO lifesupport.
"Prevents Crew Death" decreases the rate of crew loss. However, it cannot make the crew loss rate negative.
It has nothing to with crew injuries due to weapons fire.
- Major problem for later: Weapon scaling factor and Map scaling factor are zero in campaigndata.txt. This means a distance of 10 units normally is zero units long in your campaign. Very very not good.

[Phoenix-D]

That last might well be the cause of the crash..

[Tiwaking]

Thanks for everyones help, but nothings fixing it!

Suicide Junkie said:What things did you change since the last time it worked?

It's never worked. Thats the problem. It was crashing before with a nice clean "Purchase ship file has no seller! Cannot find seller ID" error which was easily fixable

Suicide Junkie said:
Some other problem areas I noticed during my search:
- Your slot layout for the Fighter is messy and overlapping. Lots of slots crammed on top of each other. Use my SFSlotmodder to help.

I made that with the slotmodder, anyone who tries doing it just with text editor is insane or a genius. According to the Starfury Haven Tutorial overlapping slots dont affect anything. I made it messy to show how the Romulans had absolutely squeezed every bit of space on the ship and had somehow added a heavy weapon launcher to an otherwise nondescript fighter.

Suicide Junkie said: - Your heavy weapon slot has the same name as your light weapon slot (#1). This is bound to cause some confusion in the default component placement routine.
- Your fighter hull has a base crew of zero.
- Your fighter hull has a base energy storage of zero.
(These two may cause issues with the bar graphs, or instant death when trying to upgrade your cockpit)

The heavy weapon slot was an accident. I must have created a light weapon slot and just renamed it to heavy in the slotmodder. Whoops
The crew and energy storage were on purpose. I've fixed those now, but they arent causing the crash.

Suicide Junkie said: - Your use of the prevents crew death ability indicates you don't quite understand how it works:
"Base Crew Death Rate Per Second" on the hull specifies how fast your crew decreases when you have NO lifesupport.
"Prevents Crew Death" decreases the rate of crew loss. However, it cannot make the crew loss rate negative.
It has nothing to with crew injuries due to weapons fire.

This was done on purpose. I thought that if a component had a say 5.0 prevent crew death, takes 50% it still has a 2.5% prevent rate. This obviously doesnt affect the fighter since it has a crew death rate of 0.0 so the only way to kill the pilot would be to.....blow up the cockpit

Suicide Junkie said: - Major problem for later: Weapon scaling factor and Map scaling factor are zero in campaigndata.txt. This means a distance of 10 units normally is zero units long in your campaign. Very very not good.

I completely forgot about the weapon scaling factor having to be set to 1. Its mentioned in the modding guide PDF by Aaron Hall. Originally I had the maps in a 13x13 scale(Same as Space Empires III) with a x100 multiplier. I thought that might be causing the crash so changed it to 0 scale. I've fixed these values up now

Thanks for everyones help. Just remember that its just a test so of course the mod will have to remain very empty until I can get my head around the proper procedures to make it work

[Suicide Junkie]

The main problem with the mashed slots, is that it makes it a pain in the *** to click components.

Well, the thing to do, is to start with stock again, and replace bits until it dosen't work.
I tried that, and got the map stuff in fine.
There's gotta be a problem with the fighter, somewhere...

[Tiwaking]

I've been thinking: Does having only one system with no exit warp points cause problems?
Also: I'd like to make a few custom slots, but with different colours from the normal slots(like Purple, Light Green, Brown, etc) How do I make the colour index point to a custom colour?

If I cant get this fighter to work, then I think I'll just straight out try the D'deridex. When you said that you tried the stock and replace bits, did you mean you tried it with my mod or your own?

Edit: I was idly trying out some ideas with the mod when I managed to 'fix' the main crash error! Turns out you were right about hardpoints. I had changed the weapon NAME to Weapon (light) 1 and 2, but forgot to change the hardpoint numbers. Now the game is generating nice clean errors again!

Could not find field "Name" in record 1.
Could not find field "XFile" in record 1.
Could not find field "Override Texture Filename" in record 1.
Could not find field "Base Model Radius" in record 1.
Could not find field "Starting Rotate X" in record 1.
Could not find field "Starting Rotate Y" in record 1.
Could not find field "Starting Rotate Z" in record 1.
Could not find field "Starting Scale X" in record 1.
Could not find field "Starting Scale Y" in record 1.
Could not find field "Starting Scale Z" in record 1.
Could not find field "Starting Position Offset X" in record 1.
Could not find field "Starting Position Offset Y" in record 1.
Could not find field "Starting Position Offset Z" in record 1.
Could not find field "Continual Rotation Vector X" in record 1.
Could not find field "Continual Rotation Vector Y" in record 1.
Could not find field "Continual Rotation Vector Z" in record 1.
Could not find field "Continual Rotation Speed" in record 1.
Could not find field "Star Glow Color" in record 1.
Could not find field "Firing Flash Color" in record 1.
Could not find field "Explosion Effect" in record 1.
Could not find field "Explosion Center Color" in record 1.
Could not find field "Explosion Radius" in record 1.
Could not find field "Number Of Firing Points" in record 1.
Could not find field "Number Of Engine Points" in record 1.
Could not find field "Number Of Lights" in record 1.
Could not find field "Name" in record 2.
Could not find field "XFile" in record 2.

etc up to record 4. Strange because, there is no record 4