Hello!

Blast from the past..

I recently found ParkCrafters and was very happy to see so much of RCT3's custom content saved. So much time and dedication has gone into creating things for this game.

I have been trying to see if this ol' guy still has it, and I am running into an issue. I am trying to make a new path, and I am currently working out the following kink:

• Texture Referencing is not working.

  • I have created the ovl files in the importer, but I am having an issue where the shared textures are not being referenced correctly, yielding me the big green blob.

    • I have created "OS_EPCOT2-texture.common.ovl"

      • I set the ref in the importer to "OS_EPCOT2-texture" (see attached image:)
        

Anyone have any ideas? I'm sure its somethings simple.

Seems silly to even ask you of all people (LOL!) this, but if I remember correctly we used to ask the obvious first - the texture is sized properly to the power of 2? Are the folder's nested correctly without an extra layer? Does the .ovl file folder include the .tex file (I recall spending a couple hours myself trying to figure out that one years ago...)? Usually I think green blob just means the .tex file isn't being accessed properly, usually either something bout the texture itself (size) or placement in the directory, although I think some people had problems with custom textures if they were using an ultra-high resolution or on a Mac.

It's been so long since I've used RCT3 that I've forgotten what little I knew back then. Hope you figure it out!

Wonderful to see you still adding to the game Mike!

Haha, I know right! I was going through files on old hard drives and I found some of my stuff, but sadly its a mere fraction. I surprised myself when I was still able to navigate the importer and create these ovls.

So to answer your questions.

• Yes, I have the textures up to a max of 512x.

• From what I can see, the Custom Path Creator has created the path properly.

  • 

    • I have uploaded the shared texture ovl that was made in the importer, here in the path creator.
      

    • 

      • It also appears to have successfully added it into the path folder, along with the other path items. (I looked at the other paths and all show the same structure)
        

• Here is how it was set up in the importer:

  • 

    • Exporting gives me the "OS_EPCOT2-texture" ovl's
      

    • Here is the OLV file for "Slope"

      • You can see that I have added the reference and named it the same as the output file.

        • 

Not sure if this is just a naming issue, or if I am misconfiguring the reference file. Was not sure if anyone old or new is working with the importer because my rapidly aging brain is not working it out!

I've forgotten most of how that even works, but your files certainly look okay from what I remember.

Several people are still making CSO for RCT3...you might message C O N S T E L L A T I O N as he is still constructing sets and posting here.

Thank you kindly - I will see if they have any input!

Unfortunately, this is the one area in RCT3 I've never touched, so I personally can't help you here, but there are others on here that still create CS to this day!

Hopefully @FrancesCoaster @C O N S T E L L A T I O N can help you out!

@Old-Spice is back at it again!

Hi There! I haven't really worked with a Texture OVL before, i usually just use the basic png or jpeg i resize in Paint.Net for my textures and i haven't worked with custom paths yet. I can forward you this link however which might help with information, im not sure if you have already viewed this but just incase.

FlightToAtlantis.net: The Compleat Path Creator, Page 1

I did have an Issue once with the importer when i was using a Jpeg Texture Wrap for a model and it just kept coming out with the slimeman texture stretched over it and when i just changed the name of the texture to something different, re-saved it and used that version instead, the importer suddenly accepted the Texture 😂 May be a situation where the importer is just wanting to give you a kick just because it feels like it.

Sorry if i haven't been of much help!

Edited June 7Jun 7 by C O N S T E L L A T I O N

This is gonna sound really stupid (consider the source), but could it be something as trivial as using a hyphen in your filename (OS_EPCOT2-texture.common.ovl) is causing the trouble? I know the Importer likes underscores (_), but maybe hyphens give it indigestion? If this is as stupid as I think it is, then just ignore me.

1 hour ago, C O N S T E L L A T I O N said:

Hi There! I haven't really worked with a Texture OVL before, i usually just use the basic png or jpeg i resize in Paint.Net for my textures and i haven't worked with custom paths yet. I can forward you this link however which might help with information, im not sure if you have already viewed this but just incase.

FlightToAtlantis.net: The Compleat Path Creator, Page 1

I did have an Issue once with the importer when i was using a Jpeg Texture Wrap for a model and it just kept coming out with the slimeman texture stretched over it and when i just changed the name of the texture to something different, re-saved it and used that version instead, the importer suddenly accepted the Texture 😂 May be a situation where the importer is just wanting to give you a kick just because it feels like it.

Sorry if i haven't been of much help!

Hey! Yes, I did find that link about 20 minutes ago and read through all the pages. (Learned that we can do recolorable textures for the bridge models!) By trying to use a shared texture file, the game will load the textures only once for all the pieces involved, instead of loading the same textures into memory, over and over each time a path piece is placed.

Flight to Atlantis says that when setting up our shared texture reference in the Importer it will automatically read

"..\shared\TutorialPath-texture"

While pre-importing path and queue models, while we are setting up the Importer to share our textures we need to change the reference:

"..\shared\TutorialPath-texture"

into:

"TutorialPath-texture"

Having done this, after they’ve been run through the Path Creator our project files and the way they link to each other will be just as this utility requires when it creates our paths and queues, and just the way RCT3 requires when we use our paths and queues in the game.

So I have done this by creating "Epcot2-texture.common.ovl" and I removed the "..\shared\" from the beginning as well. So I am completely stumped. Everything says that this should be working, but something is not working like it should.

I will be moving soon-but I will try a few different things once I am settled in my new place, and I will even try to rename the texture files to not include and underscores of hyphens.

I looked in the path folders from the paths that I made like 10 years ago, and I confirmed that they do include the hyphen in the texture file, so I don't think thats the case, and the importer also adds this by default.

The models load fine, aside form the green blob. I had some initial issues with the pieces being rotated incorrectly, but I worked through those already.

And to JB- there are no stupid questions or ideas here!

I'm stumped. And thank you both for your ideas and input!!

Edited June 7Jun 7 by Old-Spice