http://modcraft.io/viewtopic.php?f=22&t=4873

Hey there! My tutorial doesn't cover how to do what he's asking. I'm not 100% what he's asking but I definitely didn't cover porting existing Terrain in there.

@XodusArt2, each ADT as far as I know uses it's own texture coordinates via alphamaps embedded into it, so you'd have to somehow combine every single one (TextureAtlas? :s) for each texture layer, and linear interpolate the textures into a single diffuse but the amount of files needed for this (up to 4 for each ADT) would absolutely kill Unreal in most cases.

I'm gonna be a bit of a dream breaker here but Unreal tends to just be awful for these kinda things, so it's gonna be a lot more effort than exporting the heightmap as one huge file and just importing it to one Terrain/Landscape node.

The best way I've found so far to do these kinda things (Not recommended, Unreal is reaaaally only meant for small maps/Arenas) is to export each ADT as it's own mesh, then do what I said above but instance each ADT's material using texture params and a master material. But even then, you're left with little flexibility, but far more than using one piece of terrain (Because even UDK only supports 12 (?) texture samples per node) and you're also given much more LOD functionality with Meshes, so you can theoretically have a bigger map with less performance impact, AND the ability to paint vertexes, which is actually VERY important for a map like Gilneas, practically every mountain is vertex shaded.

Probably not what you wanted to hear, and if you can find a better way, please share, I've ran into these issues before (Converting Gilneas to UDK, coincidentally) and ended up just realising that WoW's file formats, especially ADT, are so proprietary and optimised for WoW's engine, converting them on a massive scale is just not practical.
 
Sorry for the text wall and good luck! ^^

I hate just quoting a link and telling you to use the search function but you really could've saved yourself the time.
viewtopic.php?f=12&t=2971

Ascathos wrote:
This is one of the more hairy topics to approach. However, I have a failsafe way to handle it. Basically, each chunk can contain 4 textures (each on a layer), which each can have a specific applied groundeffect ID. The ID is further defined within the .dbc, however, this is not important. The most important thing is simple; Wow tries to visual a groundeffect for a texture that is not existing. On a chunk with 3 layers, but 4 ground effects noted, it is bound to lead to a "false", leading to a crash.
A simple fix is easy; simply use the texture painter, apply some texture, set it to some size but the lowest speed and apply it onto the adt, until every chunk has 4 layers. The crashes stop.
Another possibility is to remove all the groundeffects IDs (MCLY) for every chunk, or even specific chunks, to avoid the problem. Refer to the 010 Editor for that.
The last one is to completely change the groundeffects according to needs. Either by hex, or getting a tool (post it once you have it.)

Refer to this section, basically make sure each Chunk of your ADT has 4 textures, sounds like you're editing Blizz ADT's and this happens almost always, if not -Always- so just check all your Chunks, then open up the texture painter, set opacity and pressure to 0 or closest and paint over the whole ADT until each chunk has 4 textures.
It won't effect your edit's as long as you make sure your brush settings are fine, but as always keep backups and recognise this isn't a permanent fix, and can cause problems later so plan around them and again, backup!
Good luck on fixing your problem and promise to check out that link I put at the top!

Hey! Just dropping a simple tool to reset the trial period on Machinima Studio - Honestly I don't know if this exists elsewhere or if there's an easier way to do it, because reinstalling and repairing did nothing for me and never has.

What this does:

- Extends the trial or resets it if it's already finished.

What this doesn't do:

- Activate the software
- Remove any wait times etc

If this goes against any rules of the forum, feel free to remove this thread, I made this for personal use anyway.
I've reset the trial twice with this, but if it doesn't work for anyone, send me the log (If it throws an exception), and I'll look over it.

As with most tools like this, the software edits registry, and therefore I can't promise it won't set off a false positive on virus software.

To manually reset the registry key, Open Regedit, navigate to "SoftwareBCMachinimaStudio" and remove "feedbackUrl"

Support the creators of Machinima Studio by purchasing a copy!

VirusTotal Scans

Download Mirror

i export the Blizzard water from map 37 then i import that water to my custom map 37
(.tele 67 if u dont know the map)

and now, when i try to make a new water with allwater.exe, i have wowerror ingame

wtf

You need to give more details and the error messages you're experiencing.

1. What are you trying to do?

2. What errors are you receiving? (Attempt to be verbose, for a proper diagnosis. I suggest Pastebin.com)

Once you've answered those, people might be able to hazard an educated guess at the very least, but you haven't given them the information to do so.

What XxXGenesisXxX said is correct, you need to re-extract the Vmaps from your client and put those in your server, rather than the defaults that usually come with repacks/Unmodified clients.

Quote from: "samgartell"

Perhaps using the default ocean shader with a plain blue texture is the way to go for the closest effect.

Most people do that.

I've just tried it, getting some strange artifacts on that too.


Going to try a blue caustic sequence with as little possible contrast, and see if it creates a nicer effect.

Is there any way to get the shader to render a bump/normal map sequence along with a diffuse?

It tends to look more like glass. I wish there was a way to port the data we need from the Cata Alpha, they're still pretty similar.

That's true, but it's a big improvement over the water we have now, with a normal map running over the diffuse, it'd look like cataclysm water even more-so.

ProceduralDepth textures not being a file is the whole idea behind _procedural_ shaders. They are generated on the fly. That's also the problem when trying to use them in 3.3.5a since triggering generating these correctly is not trivial, to my knowledge. The visual artifacts may just be a bug in the shader itself.
I'm impressed you got that far.

Ah, that's slightly disappointing, Thanks. And thank you?

Perhaps using the default ocean shader with a plain blue texture is the way to go for the closest effect. I'll make a few more attempts to improve on it, maybe look into WoW's shaders more. Would be nice to recreate the vertex animation and shoreline effect eventually. But right now it all seems like a headache waiting to happen.