[Community Project] WIP Weather & Water Shader

[Nsomnia]

@;585117

I expected the project files to be in zip format not in a directory structure. So I don’t know which files I need to download
to install or migrate plugin into my project.

But it looks like people have been having problems running it on 4.12. As that’s the version of the engine I have.

Its ran fine on every engine verison since it was an old blueprint setup. Never an i’ve been with project dayin and out since about 4.6.

It will ask you to build because theres source code!

The folders are in a directory structure (which are in a zip if you download from the repository so im confused how your saying its not one or the other when both are true) because its a demo project, hence OCEANDEMO. Simply migrate the entire content folder from the RUNNING OceanDemo projcet into your CLOSED project and then copy the /source/ and /plugins/ folder from OceanDemo to YourProject root folders and then rename the source code module names and such (see below).

You also need to edit your build.cs and your gamemodule and gamemodule editor code to be renamed for YOUR projects name, replacing OceanDemo strings, did you do that? That would cause these errors your having.

Can you post your /source/ YOURPROJECT.Target.cs and YOURPROJECTEditor.Target.cs as well as /Source/YOURPROJECT/YOURPROJECT.Build.cs as well as /Source/YOURPROJECT/YOURPROJECT.cpp and /Source/YOURPROJECT/YOURPROJECT.h as well as ensuring they are named the same as YOURPROJECT.uproject?

@;585131

If people are modifying the engine code and releasing their projects or tutorials based off their modified engine code, it is likely to cause file dependency problems when they are migrated or loaded into normal unmodified engines and is WHAT I DON"T LIKE about the Unreal Engine is all the problems with other file dependencies that it causing, all because the engine is not backwards compatible.

That’s why I can’t get tutorials or projects to run very well on 4.12 when they have been made in 4.8 ect. when i try to do them because of file dependency problems that keep cropping up, it causes problems for the blueprints and breaks the blueprints nodes and causes compiler errrors. I couldn’t get the Ledge Grabber project to migrate from 4.8 to 4.12. just crashed the engine.

The project in no way modifies any engine source. If it did it wouldnt even run most likely. LedgeGrabber may very well have a module/source/etc. that needs setting up as well. You cant expect plug and play for everything. Downlaod 4.8.3 and run ledgeGrabber so you have a reference then migrate to your 4.12.x project and see what got deprecated (depreacted means something got old and replaced with a newer “version” in the upcoming version after it was deprecated), by simply seeing what blueprint errors (or code if its code based) you have and fixing the (most likely small amount of) errors it spits out.

Its very rare I find a project from 4.4 forwards that wont run on 4.12.x as long as theres no code, and any deprecated blueprint member function nodes etc. are usually a small amount, they strive for backwards compatibility.

Another thing. When your game is ready to be developed to the public stick with an engine vesrion and leave it. pull in changes from github that you NEED and run a custom build among your team.

If you just want the plugin just download the /plugin/ and /source/ folders.

If you want the content that uses the plugin, copy the content.

If you want the whole project, do both or just rename OceanDemo to MyLittleProject in the source files and uproject and recompile and go happily developing.

Also, try delteing /intermediate/ and /saved/ and if all else fails /binaries/ and .sln: nice and clean.