You know… This game you’re creating is giving me a huge Robot R&D vibe. Just curious if you ever played that game from the (Here I go dating myself) 80’s.
1 Like
Nope, never heard of it. Glad you seem to like it though!
I actually took a bit of inspiration from MechWarrior.
1 Like
Anyone remember these guys?
Also, damage and effect sync are in. You can now battle properly!
8 Likes
Getting a large portion of my 3D model backlog into the game, reimplementing billboards.
Now with extra glass cracks.
I don’t know if I’ve shown any of the newer ones actually…
14 Likes
My GUI tends to get messy quickly, so i wrote a little appstate that provides a 3x3 grid of screen positions that you can add lemur gui elements to, and they will stack. So I can add another GUI object to the top-right, and it will stack below whatever is already there and re-position them all to be visible on-screen. Easier to see than explain.
stackableGuiState.addChild(ScreenPosition.Left_Top, statsContainer);
stackableGuiState.addChild(ScreenPosition.Center, something);
stackableGuiState.addChild(Right_Center.Center, somethingElse);
4 Likes
Yeah, this can be useful. The DebugHudState in a lot of my examples does similar (it’s part of SiO2):
The top and bottom stack horizontally, sides stack vertically.
2 Likes
So this just happened:
Joystick[0]:Saitek X52 Flight Control System
buttons:31
JoystickButton[name=Taste 0, parent=Saitek X52 Flight Control System, id=0, logicalId=0]
JoystickButton[name=Taste 1, parent=Saitek X52 Flight Control System, id=1, logicalId=1]
JoystickButton[name=Taste 2, parent=Saitek X52 Flight Control System, id=2, logicalId=2]
JoystickButton[name=Taste 3, parent=Saitek X52 Flight Control System, id=3, logicalId=3]
JoystickButton[name=Taste 4, parent=Saitek X52 Flight Control System, id=4, logicalId=4]
JoystickButton[name=Taste 5, parent=Saitek X52 Flight Control System, id=5, logicalId=5]
JoystickButton[name=Taste 6, parent=Saitek X52 Flight Control System, id=6, logicalId=6]
JoystickButton[name=Taste 7, parent=Saitek X52 Flight Control System, id=7, logicalId=7]
JoystickButton[name=Taste 8, parent=Saitek X52 Flight Control System, id=8, logicalId=8]
JoystickButton[name=Taste 9, parent=Saitek X52 Flight Control System, id=9, logicalId=9]
JoystickButton[name=Taste 10, parent=Saitek X52 Flight Control System, id=10, logicalId=10]
JoystickButton[name=Taste 11, parent=Saitek X52 Flight Control System, id=11, logicalId=11]
JoystickButton[name=Taste 12, parent=Saitek X52 Flight Control System, id=12, logicalId=12]
JoystickButton[name=Taste 13, parent=Saitek X52 Flight Control System, id=13, logicalId=13]
JoystickButton[name=Taste 14, parent=Saitek X52 Flight Control System, id=14, logicalId=14]
JoystickButton[name=Taste 15, parent=Saitek X52 Flight Control System, id=15, logicalId=15]
JoystickButton[name=Taste 16, parent=Saitek X52 Flight Control System, id=16, logicalId=16]
JoystickButton[name=Taste 17, parent=Saitek X52 Flight Control System, id=17, logicalId=17]
JoystickButton[name=Taste 18, parent=Saitek X52 Flight Control System, id=18, logicalId=18]
JoystickButton[name=Taste 19, parent=Saitek X52 Flight Control System, id=19, logicalId=19]
JoystickButton[name=Taste 20, parent=Saitek X52 Flight Control System, id=20, logicalId=20]
JoystickButton[name=Taste 21, parent=Saitek X52 Flight Control System, id=21, logicalId=21]
JoystickButton[name=Taste 22, parent=Saitek X52 Flight Control System, id=22, logicalId=23]
JoystickButton[name=Taste 23, parent=Saitek X52 Flight Control System, id=23, logicalId=24]
JoystickButton[name=Taste 24, parent=Saitek X52 Flight Control System, id=24, logicalId=25]
JoystickButton[name=Taste 25, parent=Saitek X52 Flight Control System, id=25, logicalId=26]
JoystickButton[name=Taste 26, parent=Saitek X52 Flight Control System, id=26, logicalId=27]
JoystickButton[name=Taste 27, parent=Saitek X52 Flight Control System, id=27, logicalId=28]
JoystickButton[name=Taste 28, parent=Saitek X52 Flight Control System, id=28, logicalId=29]
JoystickButton[name=Taste 29, parent=Saitek X52 Flight Control System, id=29, logicalId=30]
JoystickButton[name=Taste 30, parent=Saitek X52 Flight Control System, id=30, logicalId=31]
axes:12
JoystickAxis[name=Y-Achse, parent=Saitek X52 Flight Control System, id=0, logicalId=y, isAnalog=true, isRelative=false, deadZone=0.0]
JoystickAxis[name=X-Achse, parent=Saitek X52 Flight Control System, id=1, logicalId=x, isAnalog=true, isRelative=false, deadZone=0.0]
JoystickAxis[name=Z-Rotation, parent=Saitek X52 Flight Control System, id=2, logicalId=rz, isAnalog=true, isRelative=false, deadZone=0.0]
JoystickAxis[name=Schieberegler, parent=Saitek X52 Flight Control System, id=3, logicalId=slider, isAnalog=true, isRelative=false, deadZone=0.0]
JoystickAxis[name=Y-Rotation, parent=Saitek X52 Flight Control System, id=4, logicalId=ry, isAnalog=true, isRelative=false, deadZone=0.0]
JoystickAxis[name=X-Rotation, parent=Saitek X52 Flight Control System, id=5, logicalId=rx, isAnalog=true, isRelative=false, deadZone=0.0]
JoystickAxis[name=Z-Achse, parent=Saitek X52 Flight Control System, id=6, logicalId=z, isAnalog=true, isRelative=false, deadZone=0.0]
JoystickAxis[name=Mehrwegeschalter, parent=Saitek X52 Flight Control System, id=7, logicalId=pov, isAnalog=false, isRelative=false, deadZone=0.0]
JoystickAxis[name=pov_x, parent=Saitek X52 Flight Control System, id=8, logicalId=pov_x, isAnalog=false, isRelative=false, deadZone=0.0]
JoystickAxis[name=pov_y, parent=Saitek X52 Flight Control System, id=9, logicalId=pov_y, isAnalog=false, isRelative=false, deadZone=0.0]
JoystickAxis[name=Nach oben/unten bewegen, parent=Saitek X52 Flight Control System, id=10, logicalId=unknown, isAnalog=true, isRelative=false, deadZone=0.0]
JoystickAxis[name=Nach rechts/links bewegen, parent=Saitek X52 Flight Control System, id=11, logicalId=unknown, isAnalog=true, isRelative=false, deadZone=0.0]
Joystick[1]:FAME Studio CU2
buttons:0
axes:1
JoystickAxis[name=Achse 6, parent=FAME Studio CU2 , id=0, logicalId=unknown, isAnalog=true, isRelative=false, deadZone=0.0]
This is a joysticks.txt file generated by JME. One is a joystick, the other… a microphone.
@Devs: Can anyone explain why this happens? Is it detecting the volume on my mic?
Because for some reason your microphone is reporting that it has a joystick axis.
One of my digital art pads reports all kind of axes and buttons… which at least kind of makes sense in that case. I have no idea why your mic reports having an axis. Unless it has an sensor in it or something. Weird.
Currently working on procedural solid textures.
In the image, a solid color rock texture with normal mapping generated from the difference of voronoi noise at three frequencies.
Inspiration from Blender tutorial | Procedural rocks - YouTube
9 Likes
Prepaar to attack.
On the count of three.
10 Likes
Please don’t post troubleshooting in the monthly wip screenshot thread.
3 Likes
Playing around with some syntactical sugar in the form of Annotations.
The first image shows cleaning up AppSettings a little. Nothing amazing, but I never seem to get around to cleaning that part of my code up. Not sure if I’ll go with it or not.
Second part is adding fps monitors to appstates. You choose amount of times you want to be notified per second and give it an optional name/id for reference.
6 Likes
That’s pretty neat! I have several app states where I measure time in order to execute their function so many times a second and it just looks messy.
First underground guardian - TheWall (I know - it should be TheCannonBall )
16 Likes
Or “TheBoulder”… heheh:
5 Likes
Playing around with signed distance functions and putting some triangles around it.
SDF low poly dog - Album on Imgur
3 Likes
I have been playing with low-poly and light.
The model is some sort of course.
The wireframes are also displayed.
It seems that not subdividing the mesh causes crappy lighting effects.
This is more noticeable when ‘walking’ through the scene and letting the light follow the camera.
2 Likes
I can’t seem to tell the difference.
The higher detail one seems to get darker faster smoother.
If you want to trouble shoot the issue then a separate thread is probably good for that. Short answer: it has to do with out the default lighting matdef interpolates.