|
|||||
|
Just updated the site with 2 new actions. also added a button on the homepage for Javascript Scripting API reference (work in progress). The two actions are SplitScreen and Copy Animations. Splitscreen actions allows you to splitscreen into 2 allows to opt for vertical or horizontal split. Copy animations action allows you to use animation from a node and apply it on another node that uses the same skeleton(rig) they utilizes the new extended api and will work only with CopperCube version 6.6 onwards. Download the extensions from the website:- https://neophyte.cf/ |
||||
|
wow cool thank you but does the splitscreen do 2 player? |
||||
|
hello? |
||||
|
@edwin123, I already answered to your question in the CC 6.6 release thread, here I am just rephrasing the answer that I posted there. "@edwin123 SplitScreen only splits the screen into 2 and renders from 2 cameraviews on screen, you can use it for 2 player or online multiplayer but you need to setup or develop your game according to it then. For example if you want to place dual huds or names of players, then you also need to make sure that they allign to the screen accordingly and you might need to have dual overlays for one player on one half of screen and duplicate of the same overlay on the second half of the screen for example showing name or highscores of both the player. But yeah it is totally possible to use the splitscreen for multiplayer." |
||||
|
Update the shader action Fade object with version 1.4, this update fixes a bug that was causing issue with transparent objects when Fading-in, Both webGL and Windows DirectX platforms has been updated with the fix, and fading in now works correctly with Transparent materials( materials with alpha channel). Also, the scripting API reference has a test update, so you might see different coding syntax, or no color syntax highlighting in some places, Soon the API will be updated with code examples for each command and in the correct order. Download the updated shader action from the website here:- https://neophyte.cf/ccb_shader_f... |
||||
|
Can you please add Render To Texture command API to your website? I need to use it. |
||||
|
@guest, I am updating the API reference slowly, so it might take some time to update the API with the render-to-target command. You can use it like this if you want. var plane = ccbGetSceneNodeFromName("planeMesh1");I have been adding little features but in my opinion, they make a better difference. Like the command list on hovering shows a tooltip with the function that command does. Its been added to Scene Node Handling commands only. The code is syntax highlighted and you can copy the code with just one click. Added more colors wherever necessary to distinguish between different elements. For example, Notes are in red color, and parameters are in Green, CommandName as the title is in blue. These are little elements that have been updated. As it will not be an easy task for me to add all the commands in a single day, it will take quite a bit to update the API reference. but the process is definitely going to be faster now as I have created a template, and I am using that template to quickly fill in API commands and necessary elements. Meanwhile, you can check the API reference here. Keep an eye on it as it going to be updated on a weekly or daily basis. https://neophyte.cf/cc_js_ref.ht... let me know if you guys have any ideas regarding the API. I am also arranging the code block in proper order so that when going through the API, you can go in sequence with the commands. So that newcomers will get going easily with the flow. Also added scroll animation to the site, site contents will animate when you scroll through the content. I am not sure but I think it made the scrolling much faster and smooth as well. Hope this helps. 
|
||||
|
Could you expose the irr::scene::SVertexColorBrightnessManipulator functions? Brightness and contrast. Maybe an option to apply the new values to all vertex colors / materials? I have meshes which I can't open externally so adjusting these in the editor would be nice |
||||
|
I don't know why you need these functions, you can already use the inbuilt color picker of the editor when setting the vertex color to use Hue, Saturation, and Luminosityyou can use these parameters to do the same. For example, you can increase the luminosity to increase the brightness of the color. I think the color picker already does that for us. You can select whatever color you want from the color picker. Also, as the editor code is not exposed to us, I can't really make any changes there. I can only create API commands that will work during the runtime of the game. Only @niko can decide whether he wants to implement those commands in the editor or not. |
||||
|
Just updated neophyte.cf with all the available CopperCube versions. 65 versions for the windows platform and 49 for macOS. Also packed them all in zip archive of Google-Drive link of Windows (1.19 GB), macOS (1.02 GB). If somebody wants to try older versions, and don't have idea how many versions are available then just visit the page here:- https://neophyte.cf/cc_version_h... |
||||
|
I was browsing your site and in the "tutorials" menu the button "API Reference" takes you to the same page as the "Code Snippets," I don't know if this is intentional or a bug. |
||||
|
Thanks for reporting it @pmax, updated it on my local machine that was just wrong linking, Initially I was thinking to make the API refrence in the code snippets page but then thought of creating at as a different page, and I totally forgot to update the link in the menu bar. In the next update for the site it will be fixed, meanwhile if you want to access the API reference you can use the button on the landing page of the site. |
||||
|
Updated the site with a new extension Directional Proximitiy along with the update to the API Reference page, the API reference page is still not completed but I have covered 1/3rd of API commands, all the commands have example code, also with the syntax highlighting, I tried to include various examples for the codes instead of using same example for similar codes, unlike official documentation. I tried to make it clear what each parameter of the command has to be, and if it has to be a string then you will see it in quotes "parameter", which helps you immediately to understand if you have to use string literals, for example, the key events use a string literal for function name while the on frame event doesn't use the string format. So you can easily distinguish between them. I also tried to use multiple examples in some places to make it more clear and understandable. I will very soon update the whole API reference, along with the code examples for recently created API commands. Hopefully within a week or two. Don't forget to check out the extension Directional Proximity which allows you to execute an action when an object enters the proximity box from a specific direction. Download the extension from here:- https://neophyte.cf/ccb_behavior... |
||||
|
Just updated the Dialogue Manager extension with version 1.1. This update fixes the following bugs. - Fixed a bug that was skiping the dialogue text even if the text is reached to the final line, when the skip key is pressed - Fixed a bug that was not executing the action on finished if the skip key is pressed repeatedly when the dialogue reaches the endline. - Fixed a bug that was playing next line of conversation, if the startline and stopline are same in the action. Also updated the javascript API page with some more content, however it is not yet complete, and some of the content might have dispaly issues. you can download the updated extension from the website here:- https://neophyte.cf/ccb_action_d... |
||||
|
Uploaded an update to the extension by Hadoken Scanlines effect to have alpha controls for the color of the scanlines. Download the new update from the website. |
||||
| [ < 3 4 5 6 7 ] Page 5 of 7 |
|
|
){kind=link}