Page 1 of 1

Using default textures as additional textures

Posted: Sun Jun 16, 2013 2:08 pm
by Darknirv
Hello all, this is my first post after scouring the forum for months.

I have several texture based ship OXPs installed on Oolite v 1.76, and I use them in "addition" mode. I know that I can replace the main textures but I do like variety so having the default textures is nice.

What I was hoping for would be Griff's ships as a replacement texture pack, with Deepspace Ships AND the default textures as additions.

Is this possible? Or would I have to make a new OXP with the default textures transferred into it with an addition config file?

Re: Using default textures as additional textures

Posted: Sun Jun 16, 2013 2:38 pm
by spara
Welcome...

If you override the default set with a replacement set, you will not see the default set again. I suppose you want to use the replacement Griff's to get the asteroids and stations replaced? Otherwise you could always use Griff's as an addition.

If you are adventurous :D ... there's always the possibility to create an oxp out of the original shipset. Would not be very hard to do actually, just copy the original shipdata.plist and change all the names to something like "original_adder" or something. Maybe leaving out asteroids, hermits and stations.

Re: Using default textures as additional textures

Posted: Sun Jun 16, 2013 5:27 pm
by Smivs
Darknirv wrote:
...installed on Oolite v 1.76...
Hi Darknirv, and welcome.
You really should upgrade to v1.77 you know. Is there any reason you are still using 1.76?

Re: Using default textures as additional textures

Posted: Mon Jun 17, 2013 1:55 pm
by Darknirv
spara wrote:
Welcome...

If you override the default set with a replacement set, you will not see the default set again. I suppose you want to use the replacement Griff's to get the asteroids and stations replaced? Otherwise you could always use Griff's as an addition.

If you are adventurous :D ... there's always the possibility to create an oxp out of the original shipset. Would not be very hard to do actually, just copy the original shipdata.plist and change all the names to something like "original_adder" or something. Maybe leaving out asteroids, hermits and stations.
I was thinking that would be a suitable solution. I've got quite a few ideas for OXPs floating around in my head, so I guess that this would be a great way to start and see how the whole thing fits together, especially as I've no experience of programing and making mods etc. :D

As for stations, I've got three OXPs covering that :P PA Groove stations, Griff's stations and Deepspace's stations. I like turning up in a new system and seeing what the game decides to throw at me. I imagine that stations and ships tend to be built under license or variations crop up due to the resources available locally. Either way, companies would have a hard time distributing that many ships across 8 galaxies from a single factory.
Smivs wrote:
Darknirv wrote:
...installed on Oolite v 1.76...
Hi Darknirv, and welcome.
You really should upgrade to v1.77 you know. Is there any reason you are still using 1.76?
I'm still using 1.76 kind of by accident. I was installing Oolite on my desktop when it had next to no memory and a gfx card which was designed to replace on-board chips when the manufacturer couldn't be bothered to include one themselves. Version 1.77 had come out 1 week before and stated that there may be stability issues, and since I cut my space trading teeth on an unpatched FFE, I feared any bugs that I may encounter. When I shifted Oolite to my Laptop I had no internet, so simply copied the files over with a USB stick. And seeing that my laptop ha survived a house-fire (just, still have smoke/water damage around the screen :D ) I thought I'd take it easy on the old girl before sending her halfway round the ooniverse.

I have noticed that a lot of OXPs these days require 1.77, so (noob questions alert) Would I be far behind the curve sticking to 1.76? Is 1.77 streamlined in anyway? And: does 1.77 require more complicated programming in anyway?

Sorry for the rambling, only slept 10 minutes in the last 26 hours, been to college for welding, and drove all over the shop in the wrong glasses!

Re: Using default textures as additional textures

Posted: Mon Jun 17, 2013 2:14 pm
by Cody
Update - 1.77 is stable, and looks better.

Re: Using default textures as additional textures

Posted: Mon Jun 17, 2013 2:15 pm
by JazHaz
v1.77 doesn't have stability issues, any more than v1.76 does. There's a lot of improvements though, not the least of which is much better thrust graphics, and better AI.

Re: Using default textures as additional textures

Posted: Mon Jun 17, 2013 2:53 pm
by Darknirv
Hello! Yes I've just installed 1.77 and it worked first time in Lucid Puppy 528. I had great problems getting 1.76 working in Linux, to the point that it destroyed my full puppy install (still doesn't work right after several formats and re-installs). Now I have Oolite running purely in memory! Pretty sure XP was making the whole thing slow down by using the HDD all the time (fights were getting dicey).

I would like to thank Smivs very muchly! As it was his answer to another post (i forget which) that made me think about trying 1.77 in Puppy.

Moving all my OXPs across will hit my storage limit pretty hard (frugal install and all) so it may be time to pick favorites. :?

I'm guessing the improved AI will allow me to make quite specific ships to quite specific things.

It's playing into my hands!! Mwahahaha!!