itch.io

Just now found the problem with Particle alpha not always working right and fixed.

Will post an update on the forum.

Clouds scene node textures loaded also.

Jee, thanks for the nice donation ! - much appreciated.

That cloudscene node demo is actually in the source code of CopperCube. I added it in after getting the source files from Irrlicht website from very old archive. Took me ages but eventually got it working as had a number of incompatability issues that had to be sorted out.

See my video about the new cloud system in CC - its exactly whats in the cloudscene node demo actually - use: 

ccbGetCloudLayer(node,"tex1.png", "text2.png", true);

Use a parent node thats invisible to attach as many cloud layers as you like - cloudescenenode demo uses 3 layers and 3 different textures for that.

I will upload the 3 cloud textures into data/images of the binary zip file.

Thats interesting for sure. So you create and run the exe file but it loads another ccb file instead ? How you going to safeguard your assets in other ccb files or your not worried about that ?

So far I load the exe which then runs my custom binary and then loads ccb files. I put all my core code and array data into the exe file to stop hackers , hacking my game and code.

I have uploaded the terrain TOD ccb file on my itchio page, under:  CopperCube - extensions. If you ever use this in any commercial project you have to promise to make a generous donation here on Itchio otherwise its free.

It works but the Aurora texture replaced with another as Im using that in my game Saturn7. You will have to tweak the Aurora on/off also.

Its designed to be run with my compiled binary to work.

The graphics look better than my own game actually as I cant use a 3d mesh skydome as I make use of far plane clipping and it will be clipped. The directional light highlight looks good though - yeah ?

Your right - sorry (I uploaded to an earlier version).

Check version 2 again now and see its been updated.

The API - ccbUpdateTerrain had a bug and now is fixed. Plants on a  terrain loaded from heightmap now show as expected. Thanks for letting me know.

ccbSetTerrainSmoothing is an old API that I never ended up using so ignore. It was meant and partly did work to readjust the angle of terrain angles to smooth out sharp changes from low resolution heightmap file. It worked sort but not great so dont worry about this. You can smooth out sharp changes in photo editing software instead and works better IMO.

ccbSetPlantDefaults - this work but at the moment must be run before using ''ccbUpdateTerrain"  - I have updated the notes. The angle adjutment works fine but may need more testing on the size changes.

Any issues with Particle system fading in/out please redownload files as found a bug yesterday and its working fine now.

Will get back to you in a 1-2 days on all this....

Its turned off by default as it was geting in the way when I didnt want it - try updating the varaible amounts to turn it on and let me know if still not working.

Usauge:

#Camera.bobspeed = 0-2; use the 'Set or Change a Variable' and the name of the camera (here as "Camera") - off by default

#Camera.bobUp = 0-2; use the 'Set or Change a Variable' and the name of the camera (here as "Camera")

#Camera.bobSide = 0-2; use the 'Set or Change a Variable' and the name of the camera (here as "Camera")

use: 

ccbSetCollisionShape(node, x, y, z);

the collision x and z should match your player collide when moved size and just adjust over time using javascript a variable to adjust the Y value from crouched back to normal - Im sure you can work the rest out.

If you want to slowly bring back the player from crouch, you will have to adjust its shape over time so that happen as you like more slowly.

To turn off PP shaders (binary method) just set 'Shader_nameOn' to false but with the Action method just set the main variables adjust to 0 and it will not run then  -ie for Chromatic abberation, set:  Chroma = 0;

You setup a variable before start as 0 and then update every few ms or whenever you click etc (up to you)  in the range of 0 to 1 and apply that For 2D overlays:  use 'ccbSetSceneNodeProperty" and property type 'Image Alpha' - ie something like:

ccbSetSceneNodeProperty(node, "Image Alpha", 0-1);

For 3D statiuc mesh use:

ccbSetTransparency3D(node, 0-1);

if you are already using 'Transparent Alpha' material you can also instead just adjust Param1 (0-1) also.

To increase the value - just setup a javascript variable initially as 0, and every few ms (maybe 100) add to that variable from 0-1 or up to what maximum amount you want.

The Aurora effect is the most demanding of all the post processing shaders - I had lower frame rate with this also so its a limitations it seems unless you want to adjust how it runs and see if it looks ok. I cant improve it much beyond what it is already and unable to include into my compiled binary as the info is too much for CC default shader model 2.0 to use. Maybe one day I might work out how to increase it from shader model 2.0 to like 5.0 I think is the max for DX9.

on before start

var PP = 0;

var Root = ccbGetRootSceneNode();

ccbSetSceneNodeProperty(Root, "DreamOn", true);

ccbSetSceneNodeProperty(Root, "Dream", 0);

on every 100ms

PP += 0.01;

ccbSetSceneNodeProperty(Root, "Dream", PP);

Thanks for that - much appreciated. Hope you enjoy....

cheers ! :)

I just finished adding in the ability to adjust all the sound effect values for each sound effect.

Now ready to go and test out...

I got it to work using adjusting the property settings rather than specific API  - will update itchio and the forum in a  day or so....

what do you need to know ? - ie does it require a personal chat or can it be simply sorted out here ?

Not in you want to have all files ine the one folder - not really. 

You call your  CC exported file and name as 'app.exe' and to make it clearer you can rename the binary file needed to access the new API's as the same name as your game - should help, or better create  a shortcut pointing to your binary file in the main area but put your app.exe in a folder one level down so less chance of clicking the wrong exe.

They are both - part of the new source code done in HLSL but you can also run any Shader Action also if you like.

So I hope this is clear - all my shaders are new simple API's but running an external Action will also work. 

The only exception to this is a couple of HLSL shaders were too big to work correctly within the C++ source code of CC (shader model 2 limitation) so will only work currently using an Action like the Rain effect and the Aurora effect - all others are fine.

Why this difference exists between internal source code and running an Action is not currently clear to me but I got error messages saying it cant run very long shader code in the source yet somehow works as an Action....

ok, interesting.

I will look into adding the extra adjustments for each sound effect also - see how I go...

thanks - will take a look.

Either/OR - you can use the source code shaders I added plus any external Action driven ones - I dont see any problems there.

Whatever shaders you use they still work with all my API's no problems.

forgot to mention its only for DirectX though.

I cant see how you actually code in the different sound effect values using JIC method - have you tried it and tested fine ? - ie for Distortion - changing 'PostEQBandwidth' to something other than 2400 - does this work as expected ?

Your right - its missing (sorry).

It meant to read like this:

ccbSetSceneNodeProperty(node, Property, amt); Property: 'Paused'(true/false), 'SoundEffects' (true/false), 'SoundFX (below)', 'FXGain' (soundFX strength 0-1), 'PlaySpeed' (0-1)

SoundFX available: 'Chorus','Compressor','Distortion','Echo','Flanger','Gargle','Reverb','ParamEq' & 'Waves'

I will re-upload the new text file (API list) with this on it. The video also has this info:

You can turn fog off for specific nodes with my binary file - yes. I use it for lightning to not be coverd over by the fog and it works so if your using any mesh/billboard etc with the ability to turn fog off then will work.

Yes, any and all updates you have seen in any of my post and videos are all usuable also through API's in my Binary file. 

Both methods work actually - both non Binary using the external Action with HLSL shaders on it plus also the Binary method with a few more shaders dont in the core source code of CC - which is much better IMO, but both methods work.

I will have a look into this - maybe it can be like a weather effect on the gound... will get back to you..

Did you see the video I made - I think its pretty detailed.

Hi there, something like that I would need access to the Editor source code so I dont think I can get that working.

Most of my plugin functionality is based on running set code at certain times rather than checking something all the time like would be needed for something like that.

ok thanks for the input. I dont use CC shadows at all in my own usage so never really check that.

CC shadows look bad and has terrible performance so I never use it.

Seems to be a limitation so I will update the notes so other know, cheers.

All of my additions and improvements from an API perspective use Javascript.

If you dont know how to use or code anything in Javascript then cant help you unless its to do with a specific Action or Bahavior I made.

Try using 'Scratch' - this might be more useful for you in making games....

The API for each is written down for you in plain English plus you have a video on each one also - how is all that not enough ???

What part exactly did you try to get working but was unable to ?

So how did you go - all runs fine now ?

yes you can use this email address:  proff1972@yahoo.com.au

also mention what part exactly used to work and now doesnt - ie just the particlkes or what node exactly....

OK, can you confirm that when you use the standard free version without any binary at all running it then works ok ?

If still a problem then can you send me a test file sample so I can run it myself and find what it is ?

If your still having issues after this update the let me know:

- which version - free/Pro ?

- which API you using and are you using a shortcut with debug info and is there any specific API causing issues ?

- are you using collision with particles or nothing much new ?

Are you using particles ?

I noticed an issue recently but should be fixed now with latest uploads as of today....let me know...