I didn't ask you why it's bad. I asked you why do you upload bad scenes. Do you agree if you would spend more time on them fixing all the bugs, then you will be proud of your scenes instead of making up excuses for how bad they are?
Oh, by the way, I have been thinking about working on other motions with the cube such as changing the scale and translation, and maybe even displaying it in perspective projection. Those challenges would probably take me many weeks to learn the math, and then to design and debug the code, so would you be interested in tackling those things? You are much more gifted than I am when it comes to those sorts of things.
Oh, and I'm happy that you placed comments in your code because it helps me (and others) to understand what's going on. I just began learning about affine transformations a few years ago, and now using the math in a real-world application helps me to understand most of it. Thanks again!
You would not hear anything because that square wave has a repetition rate of about 30 seconds, which is well below the range of human hearing. You might hear the rising and falling edges of each pulse due to harmonic content, but that would sound mostly like a "click".
How do I know this? I have a wide-range function generator, oscilloscope, and audio amplifier that I have experimented with a long time ago. That generator can make some really weird sounds!
s_noonan -- There's a little glitch in my code that always bothered me and I see that it transferred over to your scene. When rotating x, y, or z axes there's a little "hiccup" that occurs when the theta switches from -pi to +pi OR from +pi to -pi. I found that the transition can be made a lot smoother by adding a small +0.1 or -0.1 offset when the transition occurs. Here is the code change that seems to work well. Try it and let me know what you think about it:
Quote: "...I'm wondering why the code has the +/- math.pi limitation"
Reply: I think it's because rotations are calculated in radians, but not sure. There are 2pi radians in 360 degrees, which might explain the +/- math.pi limits.
Please don't make a habit of copying and then uploading other people's scenes because it's frowned upon here on Algobox. Only upload scenes that YOU have created. Thanks!
Quote: "The only issue I see with removing the limitation is that if you did enough rotations, the angle could be so large that the angular resolution suffers."
Reply: I didn't think of that, but you are right.
More: I like how you changed the code to make a smooth rotation. I won't blame you at all if you decided to not add variable scale and translation because the code has gotten rather complex at this point. Adding more features might muddle the design. You already have done some very impressive work in my view.
Because you clicked the word "Subscribe" which is just above the Rating bars. When you are subscribed to a scene, you will receive an alert (Message) every time the scene is updated and every time someone submits a new comment. If you subscribe to the User, then you will receive all new scenes and all updates that the user uploads. If you no longer want to receive alerts, then click on the word "Unsubscribe".
I (or someone else) may be able to help you if you can be more specific about what you are trying to do. Simply stating "I can't make an arch" really doesn't explain much at all. Explain how large the arch needs to be, and how you plan to use it in your scene. The more details you can provide, the better someone's answer will be for you.
Quote: "If we don't use perspective projection on the cube then there should be a way to make the image fit."
I agree, but it just isn't working out for me. Your code is a lot different than mine, and because of that I'm having trouble understanding it and getting it to work. I don't have the coding knowledge and experience that you have which makes it much more difficult for me to attempt to modify it. I might be able to get something to sort of work, but it will take a lot of time, and you would probably point out how it could have been done more efficiently in terms of lines of code and execution speed. So, I'm hoping that you would still be interested in taking on the task of doing those things that we have discussed earlier. I'm always impressed by the awesome Algodoo scenes that you have posted over the years, and I learn a lot from them, as I'm sure others do too.
s_noonan -- I tried using a reciprocation dingle arm but the parasitic oscillations were causing standing waves of the 3rd harmonic when I added power. After I removed the dingle arm and inserted a revolving hex nut vestigial transformer, I got much better stability in the magnetron filament circuit. Thanks!
42flowermaster -- Well you would need to complain to Google because it showed me lots of Roblox characters and this was one of them.
This scene has a couple of issues. 1. It takes over a minute for the scene to load, which indicates that you probably have a lot extra geometries or water. I didn't take the time to find out what's causing it, but you should try to reduce the load time if possible. Try to keep it under 10 or 15 seconds. 2. When I click RUN, the camera zooms to "Floor 0 Room 2". 3. The camera zoom value seems a little too large because each test panel doesn't quite fit on my display. Maybe other users have the same issue?