reepblue

Pay the fee, get the appid. Having a repo on Steam allows for easy private testing and you can get started on integrating some Steamworks features. Some features like Leaderboards, Stats, and (surprisingly) Steam Input will not work until your Store page is live. I was in your position when it came to Cyclone but people encouraged me to put it on Steam because they want all their games on one place. Stay away from EGS, they are criminals, lol.

This extension will convert a material to DDS. Right-click on an image file in the asset browser, select the "Convert Textures to DDS" menu item, and the file will be created with the correct compression based on the type. ConvertImageToDDS.lua

I've noticed this issue too. Compiling the application not as a console application usually solves the issue.

I was actually using the drop down menu for material under appearance like you would in Leadwerks. I didn't know you could drag and drop the material to a sprite. If you do use the dropdown, the material will not apply nor save it's selection. I think the solution would be to remove it and have only one way of assigning materials to objects by drag and drop.

The selected image also doesn't save after deselecting the entity.

Here's a lua version of this. Some minor differences and I removed the use of camelSense since the stock components don't use it. This was on my list so thanks for writing it! Animation.zip

I'm trying to create an extension that'll allow quick material generation by right clicking on the image and selecting "Convert Image to DDS". The documentation with String:Right for lua isn't right and I think it's better that the extention should get the suffixes from the editor's config. Because of limited documentation on the addon system, how would I do this? The bad code is commented out for now. if event.id == EVENT_WIDGETACTION then if event.source == extension.menu[1] then if program.assetbrowser.selectedfile then if program.assetbrowser.selectedfile.package == nil then local imageext = string.lower(ExtractExt(program.assetbrowser.selectedfile.path)) if imageext == "png" then local file = StripAll(program.assetbrowser.selectedfile.path) --[[ -- TODO: Get the conversion suffix from the editor. if string.right(10, file) == "_normalmap" or string.right(7, file) == "_normal" or string.right(4, file) == "_dot3" or string.right(2, file) == "_n" then extension.ToTexture(program.assetbrowser.selectedfile.path, ".dds", TEXTURE_BC5, true) elseif string.right(13, file) == "_displacement" or string.right(7, file) == "_height" or string.right(5, file) == "_disp" or string.right(2, file) == "_h" then extension.ToTexture(program.assetbrowser.selectedfile.path, ".dds", TEXTURE_RED, true) else extension.ToTexture(program.assetbrowser.selectedfile.path, ".dds", TEXTURE_BC7, true) end ]] end end end end

The fix came up during the hangout. Might get fixed in the future but for now: Line 171 in PBR/Lighting.glsl. u_MipCount = 6; //textureQueryLevels(textureCubeSampler[shadowMapID]);

When changing a model's material pickmode value to false, the changes don't stick when reopening the model in the asset browser.

I wish I knew. I was just creating brushes and then it it stopped. I probably had a good amount of brushes in that session before it gave out on me. It was like when I lined up the brush exactly where I wanted it to build, it wouldn't make it. But if I quickly built the brush in a different spot, it worked as expected.

I'm curious why if a material has a roughness of 1.0, it's still reflecting the scene with a probe. I want this texture to be 100% mat. { "material": { "displacement": [ 0.05000000074505806, -0.02500000037252903 ], "metallic": 0.0, "pickmode": true, "roughness": 1.0, "shaderfamily": "Shaders/PBR.fam", "shadow": true, "texture0": "./Textures/wall02.dds" } }

After playing with models, I got this result previewing a material.

Please see the attached video. I want my textures to be in their own subfolder but saving the model causes it to generate and link the textures relative to the model and I'm unable to reassign it. Every time I save it, it forces the texture to be in the same folder as the model! 2024-01-28 20-03-09.zip

Latest beta.

In my current map, creating a new brush and then hitting enter fails to create the brush. Here are videos of me trying to make a floor brush. brushesnotbuildingsobemoji.zip

If you were to save this as a material, open it the editor, then do File -> Save on it, the custom property (myproperty) will be deleted. { "material": { "displacement": [ 0.05000000074505806, -0.02500000037252903 ], "metallic": 0.0, "roughness": 1.0, "shaderfamily": "Shaders/PBR.fam", "shadow": true, "texture0": "./grid01.dds", "texture1": "./grid_normal.dds", "myproperty": 1 } } I want to store the surface property in the material without worrying about it getting overwritten.

Because I wanted zooming in my game. 😭

Seems you can see some artificing with the cluster rendering when having the camera preform a zoom, The best way to demonstrate this is to install this component in a CPP project and replace the character in the start map with a simple camera that has this component. Use Z and X to toggle zoom. The zoom out code isn't right, but that's not important. I just recycled code I already had. Also, I might add that the starting zoom value needs to be stored on start because Zoom affects the camera's FOV value. Zoomer.zip

Somethings I've brought up during the call. General Beams (Like lasers but just stretches a sprite between one point to another w/o a raycast.) Script (For loading and calling lua script functions.) Ballsocket (For swinging ropes, lights, etc) Tag Filters (Used with triggers to only allow entites with certain tags to trigger.) An Animation Controller (Used to animate models that otherwise don't need any additional functionality. Logic Relay (Much like the one I posted) Random Outputs Auto Save Like I mentioned, I recorded the conversation so we can refer to that.

The separate window is the better route imo but I also hate losing the window. It's much better when you got a dual monitor setup though. I really don't like the idea of "It has to be one way or the other" since everyone had different setups.

Download the AmbientNoise component and scale the right sidebar around.

You can remove any listing from the Scene Tree by dragging the item out of the list.

When using the Print Message component (Found here) the message value doesn't save.

Wanted to get a start on these after today's discussion. Here is the first draft of the logic components. I'm kind of limited on what I can do without any argument support. I've made the following: Auto - Used to start things on Start or Level Load. (Inspired by logic_auto) Relay - Used as a switch or a delay between connections. You can toggle the component to cut or rejoin connections. (Inspired by logic_relay) RelayTimer - Fires outputs on every interval. (Inspired by logic_timer) PrintMessage - Simply prints whatever to console. This is only my first draft to continue the discussion! Logic.zip