Makrom
-
Posts
96 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Bug Reports
Posts posted by Makrom
-
-
Hello there, is this mod alive? I found it very nice and start a campaign on rp1 with it, so far has been fun, but I want to ask about an specific mission named skylark-1, the requirements say an apogee of 800 km (!), with a mass of 1,5 tons.......I don´t think that´s possible, if it were 200 km could be done with a two stage sound rocket, am I missing something?
thxs
-
Great, I´m already waiting for this, best of luck and have a great year
-
Confirm, cargo gets destroyed under fairing, it seems that they are not protecting the cargo at all
-
1 hour ago, Bej Kerman said:
I assume the navball and "ECEF" speed readout is from Principia? Have you checked to make sure Principia is compatible with this and Sigma?
Yeah, I was needing to start a fresh game, that solves the issue
-
hello, sorry if this as been asked before, I just have installed this mod, all the installation process looks fine, but when I try to launch a rocket, ship or whatever, everything "slides" to the south, making impossible to do any launch...any clue?
thanks
ksp 1.12.3, resized to 10x (sigma installed), homeswitch to efil, kerbol system disabled, wormholes disabled
-
-
7 minutes ago, kspbutitscursed said:
did you use the gitlab download
? ...is there are other installs?? of course I use the gitlab , I take it from this forum actually....
-
I swear I follow the instructions..... eve and scatterer are installed (latest versions) ksrss textures are installed (8k) any clue?
thanks
-
Just want to say thanks for your work on this useful tool, it allows me to successfully edit craft files for to be used on another save, which could have been something painful just editing text.
-
When I load a vessel from the tracking window, and after doing some stuff with it, I´m not able to go to space center o go back to the tracking station via the menu called by the ESC key.
[LOG 21:10:03.110] Game Paused!
[LOG 21:10:03.110] [UIMasterController]: ShowUI
[EXC 21:10:06.100] NullReferenceException: Object reference not set to an instance of an objectThe only way to get out of the " scene" is loading the persistent or a quicksave.
This start to happen recently, not sure if totally related to TSE, but it is when I use it that I got the error.
LOG:
https://www.mediafire.com/file/g2n3wvq11vx27ap/KSP.log/file
hope this helps
-
1 hour ago, OrbitalManeuvers said:
Inside the KSRSS-Reborn.zip file you'll find a folder called KSRSS-Reborn, and inside of there is a folder called KSRSS and that's the folder you want to copy to your GameData. The final path should be GameData/KSRSS.
geeeezz!...being caught in such a basic noob error....in my defense, there was no explicit info about it on gitlab
thanks!
-
On 6/25/2023 at 1:55 PM, ballisticfox0 said:
I assume you have parallax installed? make sure you remove the
Parallax_StockTextures/_Configs
Parallax_StockTextures/_Scatters/Configsfolders.
If you don't or the issue persists send your log
No parallax or other mods installed apart from the recommended on gitlab, simptoms: black screen, infinite loading.
LOG
https://www.mediafire.com/file/g2n3wvq11vx27ap/KSP.log/file
-
On 6/23/2023 at 12:24 PM, ballisticfox0 said:
The issue is not related to KSRSS but the .dll in KRPC failing to load properly.
Also please please please please do not upload your KSP.logs as pdfs, it will add a new line after a certain point making it a hassle to figure out what actually caused what
I confirm, errors loading with kopernicus on ksp 1.12.5, I try with a old kopernicus version and still the same, I tried with ksp 1.12.3 exact same error.
Black screen loading
-
any update on sight?
-
4 hours ago, Arrowstar said:
Okay, how about this. Can you give me orbital elements for the vehicle immediately before and after the Kerbin departure burn when you execute it in KSP?
I think I got it, taking care of closer timing and some tweaking on the final trajectory in Principia.
Here you can see the differences between the data as come out from LVD and the tweaking on Prp
In timing, LVD show 217 days, 4 hours and 33 minutes, in Prp is 217 days, 4 hours and 20 minutes, pretty close inmho
and this is my last test, to the left you see the LVD output without N-body gravity, to the right, the same maneuver but this time with N-body gravity, as you can see, there is no difference between both data outputs, except for the time, not sure if this is right.
-
14 hours ago, Arrowstar said:
Can you send me a picture of what the trajectory looks like when you use the burns in KSP as provided by LVD? And can you send another picture with a close up of the Kerbin departure burn?
Here's why. I suspect that your departure burn isn't being modeled correctly and you're not in the right place. That is, the true anomaly of the burn is probably not where you think it is in KSP. There's basically no way for LVD to be as off as you're showing it is without there being a modeling error somewhere. If you track that down, you should have the answer to the issue.
I already did that with the previous pic, there you can see the trajectory as it results with the parameters provided by LVD, there s only 1 burn, principia predictions are very accurate, so there´s no need to do the burn.
I agree with you that there is a problem with the timing, that´s what I have seen from the beginning of this post, but, afaik, I just put the parameters provided by LVD into principia, with the results already known.
-
1 minute ago, Arrowstar said:
Thanks! And which part of the scenario is the problem? Where are you not getting close enough?
Here, this is the application of the maneuver of that file into principia, I tweake a bit the time, I forward 215 days for the time of the maneuver, also I tweak the timing of the maneuver as much as I could, as you can see the predicted trajectory is not even closer to the orbit of venus, , on the venus frame reference, the ship is very far, is not like the proposed trajectory of ksptot,
-
1 hour ago, Arrowstar said:
Could you provide me with the LVD MAT case file you are working with? It can be hard for me to understand what you're struggling with without being able to see it. Thanks!
there you go
https://www.mediafire.com/file/d3hjmms6g2fxe1t/test_.mat/file
-
21 hours ago, Makrom said:
Adding the propType = numerical_integration to the .ini file throws an error on startup about "epoch must be the same for all the bodies" or something like that, so I skip that step.
Doing the third body gravity thing and running the "optimize mission" downs the time to fix in principia from 1 hour to 14 minutes, so I think it´s better
okay, I´m using the multi flyby maneuver tool and LVD, I can do the trajectory and translate it to principia with some tweaking, but still got far from the planet, can´t find a way for to predict the desired altitude.
Update: after some testing I could see that the data for prograde/normal/radial using third body gravity in every event is not different from the data without it, the only parameter that does change is the time for the maneuver, I could be doing something wrong, but that can explain why I can´t translate the data to principia accurately, not sure if it is a bug, but it is my experience until now.
-
2 hours ago, Arrowstar said:
Alright, here's what you need to do to start, I think:
- Restart KSPTOT entirely.
- Make the bodies.ini file for your configuration. Open up KSP, go to a spacecraft or any rocket on the pad. Then in the main KSPTOT GUI window (with the porkchop plot), File -> Create Bodies File from KSP.
-
Update the file you just created to use numerical propagation for the celestial bodies, as I think this is what Principia is doing under the hood.
- Add the following to each body's entry: propType = numerical_integration
- Just as a warning, this can be pretty slow, so if you can get away without the numerical propagation of the celestial bodies, I would skip this step.
- Load this file. File -> Load Bodies From File.
- Re-open LVD.
- Turn on Third Body Gravity. Scenario -> Edit Initial State. Push the Edit 3rd Body Gravity Properties button. Select the bodies you want to use.
- Turn on the 3rd body gravity model. Open up your first event. Select the Force Model Propagator. Hit the Propagator Options button. Select 3rd Body Gravity and save/close the dialog.
- Repeat this last step for each event in your mission.
Let me know if this helps!
Adding the propType = numerical_integration to the .ini file throws an error on startup about "epoch must be the same for all the bodies" or something like that, so I skip that step.
Doing the third body gravity thing and running the "optimize mission" downs the time to fix in principia from 1 hour to 14 minutes, so I think it´s better
-
13 minutes ago, Arrowstar said:
Thanks for the info. In LVD, do you have third body gravity forces turned on? And are you using the Principia bodies.ini file that I include with KSPTOT?
Not sure if it´s related, I select the sun and mercury as third body gravity properties in the window for to edit the initial state, didn´t found any option for to "turn on" third body gravity forces on the menus.
I saw the principia.ini file when I install the app, but it says bodies_STOCKPrincipia.ini, and I´m using RSS so I thought it was not a file that I could use, as principia can be used with the stock system also.
-
K, Got some questions
I design a flyby from earth to venus and then back to earth, using a ship of 35/10 tons.
https://imgur.com/oNOLBd5https://imgur.com/oNOLBd5
In LVD, the initial spacecraft state show one UT time (I think is the beginning of the window launch..) and the maneuver upload to ksp dialog shows another UT time (I think the moment when the maneuver should be executed)
Translating the numbers the initial state is at 162 days and 19 hrs, and the maneuver date is at 217 days 9 hours.
https://imgur.com/yIG46Slhttps://imgur.com/yIG46Sl
but in principia I don´t get the desired trajectory.
Now, if I subtract 1 hour to the maneuver date (217 days 8 hrs) i got this
which is kinda closer to what LVD projects, at least in the trajectory.
So, there are something related with timing that I´ m not seeing? maybe I´m not reading the right numbers?
I´m using UT, as in the game (RSS+RO+Principia) the time starts at year 0, day 0
thanks!
-
6 hours ago, Arrowstar said:
- It sounds like what you're doing is a bit more complicated that RMS was designed for. You'll probably need to use the more general purpose LVD. All RMS does is give you a transfer orbit and DV vectors to hit your desired target exactly. You can't specify a target orbit because it was really designed to be used for rendezvous with spacecraft.
- RMS definitely doesn't work with Prinicipia. If you want to go N-body, you'll need to use LVD. It's the only tool in KSPTOT that can handle that, but I'll tell you up front that the learning curve for n-body gravity is a bit steep. Feel free to ask questions!
Yeah well, it seems that LVD is something more complex related to design and plan every stage of a ship/mission...a tutorial or example could be useful.
Will start doing a multi flyby maneuver for to transfer it to LVD for to have a start point
-
Okay, I´m wondering how do I set the periapsis for the destination body, I can use the SMA parameter but I´m not getting the desired results, also, it seems that the tool, at least with the option I´m using (RMS) it considers circular orbits, but I can´t make it work reasonably with orbits with a high eccentricity, by example, for a trip to the moon, a periapsis of 600 km and an apoapsis of 2000 km can give you a boost of about 500 ms DV free..not sure how to use that with this tool , but anyway I´m just starting to use it...and also I can see that the tool doesn´t translate the data to principia, so I have to enter the numbers manually
Contract Pack - History of Spaceflight - V1.0
in KSP1 Mod Releases
Posted
yep, I agree, as stated on the document (thanks!) in 1976 Sl302 reach an altitud of 278 km and the last Skylark reach 252 km, so I would take that as a average, and in my tests I have already reached a maximum altitude of 300 km with a three stage sound rocket, so I´m ok with this contract.