Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
My first plug-in experiment, for my own benefit, was to add a ship I made into EVO, to see if I could handle playing around with the basic resources and get the sprite to work. I used The Docks by Kane O'Donnell to put the parts together into a plug-in, and that seemed simple enough. After realizing it was using the pict resources numbers for first the shuttle and then the heavy freighter, I used res-edit to give them numbers that weren't being used. So that solved the problem of my ship being odd sizes and the shuttle/freighter getting the wrong graphic. So now everything worked nicely within the game, except some odd characters after the shipyard/hire descriptions. My problem is when I remove the plug-in from the plug-in folder. When I start EVO without my plug, it runs into an error while loading (when the splash screen is up) and says it is probably due to lack of memory, which is not the case. Anybody had this problem and/or have an idea how I can fix it? Any help would be appreciated.
------------------ Vocatus atque non vocatus Deus aderit.
I don't know 'The Docks', but it sounds like it may have damaged your Override Graphics file. Try replacing it with a clean copy and see if that fixes it. If it doesn't, try doing the same with the data files.
------------------ David Arthur (url="http://"http://davidarthur.evula.net/")davidarthur.evula.net(/url): MissionComputer and the Talon plug-in (url="http://"http://www.ev-nova.net/")EV-Nova.net(/url): Forums / Classifieds / Upcoming Plug-ins / More
Did you buy another ship that comes with EVO when you removed your plugin, or did you keep your custom ship with an unused ResEdit ID number?
------------------ Kalos. (url="http://"http://www.wheenit.com/monkey-robot/")Monkey-Robot(/url)
If that's the case, removing the "Last Pilot" alias from your Pilots folder may well fix the problem.
------------------ "Insert witty quote here." - Thomas Castiglione
David Arthur As far as I know The Docks doesn't modify any of the original data files if you're working on a new plug, which I was doing. I think the graphics problems I had were because the pict ids in my plug were using the same numbers as the picts for the ships I mentioned in the main EVO Graphics file - nothing was actually replaced as far as I can see. I will try your suggestion however!
Mahayana When I removed the plugin, I also removed the pilot file I had used to test it, and the last-pilot file.
Quote
Originally posted by Valiant Bastard: As far as I know The Docks doesn't modify any of the original data files if you're working on a new plug, which I was doing. I think the graphics problems I had were because the pict ids in my plug were using the same numbers as the picts for the ships I mentioned in the main EVO Graphics file - nothing was actually replaced as far as I can see. I will try your suggestion however!
All I can say is that unless the data files or application were in some way altered, there's no way your actions could continue to affect the game after your plug-in and pilot file were removed.
I just noticed something else, which would confirm what you say - when I try to open some of the pilot files from before I used the plugin, I get an error saying the pilot file was made by a different version of EVO. Now I realize the value of making a back up of all the data files.... if only I'd realized it earlier.
Does anyone have some experience with The Docks? It's a nice application, with some good features, but after this I think I'll stick with Res-edit until/unless I find out what went wrong.
Thanks for the help!
Originally posted by Valiant Bastard: **I just noticed something else, which would confirm what you say - when I try to open some of the pilot files from before I used the plugin, I get an error saying the pilot file was made by a different version of EVO. Now I realize the value of making a back up of all the data files.... if only I'd realized it earlier.:)
**
Yeah...after early, shall we say, "experiences" with EV-Edit, I've stuck with ResEdit ever since.
------------------ Mike Lee (Firebird)
I had a few problems using 'The Docks' also. If you want to make some (mainly bug free) ships, then I suggest using 'ShipWrite.'
------------------ Shouldn't there be something in this space?
Originally posted by Captain Will: **I had a few problems using 'The Docks' also. If you want to make some (mainly bug free) ships, then I suggest using 'ShipWrite.'
Stick with ResEdit. It's practically flawless when it comes to making plugins. EV-Edit is a POS piece of software. It messes with the plug more than the designer.
Matrix
------------------ "Nothing is fool-proof to a sufficiently talented fool."
I've seen enough posts about EV-Edit and what it's done to people's plugs that I've never entertained the idea of trying it. I'm not against doing things with Res-edit alone, but if there's a tool or tools that can do the same work and are nice to work with, then why not use 'em I say. I have ShipWrite downloaded as well, I'll give it a go next time around.
Oh yes, things worked fine with a new copy of EVO - with and without my plugin. Problem solved, but not understood.
Originally posted by Valiant Bastard: I've seen enough posts about EV-Edit and what it's done to people's plugs that I've never entertained the idea of trying it. I'm not against doing things with Res-edit alone, but if there's a tool or tools that can do the same work and are nice to work with, then why not use 'em I say.
The reason why you should be wary about using third party editors besides ResEdit? While I'm not knocking the abilities of the makers of those editors (I certainly couldn't do better. I barely got past "hello world."), you have to rely on their ability to reliably convert the information that you enter into useable resources. You should always double check your work in ResEdit until you can be sure that the program is relatively bugless. That's how I found all those damn problems with EV-Edit. Hardly anything that I put into that program looked remotely like what I had intended.