Is there anything noticeably *better* about it?
Is there anything noticeably *better* about it?
No idea. I'm a retired IT guy, so I could definitely run it through it's paces as a UAT if asked. I expect there isn't a UAT at this point. The program is quite complex and it would be easy to break something when it's changed.Does anyone know if this software is independently QAd or if there has been any kind of UAT? Seems these issues should have been caught as the use case for each is quite basic and common.
Fonts are much more readable.Is there anything noticeably *better* about it?
Thanks for sharing.I use Mac OS and my RS 10.1 woes are:
1. opening a new rocket file while another rocket is open will sometimes crash the program. There is no workaround.
2. Selecting a component from the database by double clicking it will instead load the next component in the list (e.g., select the fourth component and the fifth one is loaded). However, selecting the component by clicking it once then clicking [OK] works as expected.
3. drawing custom fins and removing points does funky things to the drawing section on the screen yet the fin preview on the rocket looks correct. The workaround is to exit the wizard and then go back into it.
4. When entering custom fin points, via the coordinate list, will crash the program. This is seemingly random. It’s happened to me every entry and may also not happen at all. But, it happens more often than not. There is no workaround.
All of these issues are significant and need resolution. Does anyone know if this software is independently QAd or if there has been any kind of UAT? Seems these issues should have been caught as the use case for each is quite basic and common.
4. When entering custom fin points, via the coordinate list, will crash the program. This is seemingly random. It’s happened to me every entry and may also not happen at all. But, it happens more often than not. There is no workaround.
Open Rocksim first and then open the file you want. I assume it places the C folder somewhere within it's folder structure in the Appdata subfolder. If you double click a .rkt file in the directory it is stored to open Rocksim, it creates the C folder in that directory. Weird.What's with the C folders? I tend to store my sim files in many different directories, typically in folders dedicated to each rocket where I store other information pertinent to the rocket. When I want to look at or run simulations, I just double click the .rkt file to start RockSim (I use the Open with option to register RockSim with the file type.) Now is see a C folder in each of the rocket folders. Inside the C folder there is another folder, logs, and inside it is a text file named rocksim.log. It seems to contain information chronicling the start-up process, something that might have been useful during development.
Is there any way to turn this feature off. While it seems to cause no harm, the clutter is a little annoying.
I just ran into a similar issue in the last couple days. I found if I restarted from the launch window and rechecked the flight events , it would deploy the streamer and chute and the desired settings. I did notice something when looking over the display details that I'm unsure of--the decent speed at chute deployment was noted as 122 MPH. Does that sound correct when using a single deploy with a JLCR? I had to install a "phantom" chute in the rocket components in order to get RS to recognize the JLCR event. Is RS not realizing the rocket is "tumbling" from ejection to chute deployment?I'm having a problem with simulations in the updated Rocksim 10.1. The rocket has a streamer going at apogee and a parachute at 500' (Chute Release). The sim is having both ejected at apogee. Occasionally, the parachute will be noted at a different altitude than apogee, but not at 500'. Also, occasionally, the deployment altitude for the parachute, which had been set at 500', displays in a later run as 152.4 (which is 500' in meters). .rkt attached. Anybody else having issues with simulation results?
...Or how about where I can enter 54/1706 and it shows all the motors for said case???...
Keep in mind that the motor file formats (.eng and .rse) do not include the case size, so Rocksim has no way to know that information. Only recently did Thrustcurve include case as a search criteria.
All these 10.1 issues being reported are really weird. I can't imagine Apogee would release such a buggy version. v10.1 may be the first one by the new developer guy, and he is trying to do things HIS way, and it is isn't working as expected.
I always deploy a phantom apogee/max delay event with a dummy parachute or streamer when I am using a JLCR. Rocksim has no idea what a JLCR is. My assumption has been that if you have only a main and tell it to deploy at 500 feet that the software will assumes a ballistic return to that altitude. How would it know any different? Doing this worked fine in V10. It's screwed up in V10.1.I just ran into a similar issue in the last couple days. I found if I restarted from the launch window and rechecked the flight events , it would deploy the streamer and chute and the desired settings. I did notice something when looking over the display details that I'm unsure of--the decent speed at chute deployment was noted as 122 MPH. Does that sound correct when using a single deploy with a JLCR? I had to install a "phantom" chute in the rocket components in order to get RS to recognize the JLCR event. Is RS not realizing the rocket is "tumbling" from ejection to chute deployment?
Enter your email address to join: