-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSTU Modifications for RO #1625
Comments
I've started with the tech limits master...assassinacc:SSTU_PartUpgrades |
Fwiw SSTU's modular SRBs show zero thrust and a burntime of NaN on the VAB. I can't code to save my life (learning though!), otherwise I'd gladly help. |
Going to note issues here as I find them, may work on some later:
|
|
|
|
Is it supposed to be jettisoned during thrust phases? Every render I saw this far had the LES jettison at main stage separation before the upper stage ignited. Might be due to video and entertainment purposes of course. |
|
@Theysen you could be right, I haven't looked at the animations |
@blowfishpro Jettison side panels of the Orion European Service Module worked fine for me when I tried it (SSTU-0.5.34.134) |
I was on the dev branch. That might be the difference. I'll check it in vanilla SSTU as well, as the problem might be there. |
Just thought I would add -- if anyone needs any plugin-side changes made to SSTU to make the RO fixes possible, please let me know (PRs welcome as well, and preferred if possible). (I realize this is a long-running / older issue ticket, but many of the problems still seem relevant) |
@shadowmage45 As of right now, the actual big thing holding SSTU for RO back is 1.2.2 and not being on 1.3. I have no idea if that would even work and can be achieved - I highly doubt it - but a backport of 1.3 plugins to 1.2.2 so we can use all those new features like recoloring etc is out of scope right? Currently we have no ETA for a version bump for 1.3 and SSTU keeps on drooling with new features. Don't consider this as any request actually or something else, it is just a question but I'd assume I can give myself the answer. As for any other changes pluginside, I'd actually just could think of making the AutoDecouple feature a procedural where the input timer can be set by the user. The SSTU suite in general for RO is (imho) on its way to replace almost everything once we get a good grasp on everything new aswell. |
1.3 RO should be relatively close, I think there were only a few things we were waiting on |
IIRC the RO team was awaiting the 1.3.1 release to happen, since the localization implementation on KSP 1.3.0 affected the overall performance. It is also one of the major bullet points in the changelog. |
@Theysen -- a backport would be fairly labor intensive, mostly due to having to recompile the shader packs, as well as fix the actual plugin code; not something that I will be doing, however I wouldn't be opposed if someone else wanted to undertake the task. Auto-decouple timing slider -- sure: (will probably be available with the next release) |
Has anyone looked at the mass and thrust? For the ones I've compared (J-2, J-2X, F-1 and F-1B) they typically are 50% more massive and have 40% of the thrust of their real life counterparts. (those are approximate figures, it varies from part to part) I can't find anywhere in the repository where these are being adjusted (some plume configs and parts resized but that's it) |
They're all using the enginetype presets, I suppose there is a hickup with the modules of SSTU and the way RO Global configs patch the engines. I heard from multiple users that engine masses were wrong once clustering happens via the SSTU slider. I actually also don't know how feasible it is to fix this before going to 1.3.1 because SSTU changed A LOT since 1.2.2 compatability. I guess a complete overhaul is needed? |
@Theysen so you're saying there is or was a means of scaling the thrust and mass for these engines aside from directly setting the mass (in the part) and the thrust (in the engine module)? Can you elaborate on that and point me at the relevant files? (FYI they definitely do respond to setting part mass and engine maxThrust as one would expect and it works with clustering so it's definitely feasible, just needs the 'elbow grease ' so to speak) |
Ok, after scouring the hell out of the repository - ALL branches, I finally found a branch (e1_engine) where some engines had mass adjusted and some had thrust adjusted, or both. But either it never merged with master or dev or the changes got reverted.. |
I've been running the dev 1.31 RO + RP0 for a few days and I can't replicate the thrust issue with the SSTU engines you describe - the thrust seems to match up exactly with the non-SSTU versions, including clustered versions. I do see the mass problem though. Specifically, a SSTU cluster is (2n-1) times as massive as it should be, so the single engines are fine but a cluster of 4 has the same mass as 7 equivalent engines etc. I can't see how the bug occurs but perhaps this will offer a clue to someone else. As for the rest of SSTU everything is working fine for me except:
|
Re: Engine-mass issues -- When set to false, all mass adjustments should be handled by ModuleEngineConfigs. If this is not the case, please let me know and I can investigate further. Could also be the case that I'm not updating the ModuleEngineConfig properly on cluster # changes, but I'm far from an expert on RF / MEC setup or use; if there is something that needs to be changed in this method to clean up compatibility, please let me know -- |
OLD |
I will post about issues I have found and what needs to be / should be fixed. I will include some check boxes so that I can show you what I have completed.
Apollo
SSTU Procedural Tanks / Parts
Global Test Flight
The text was updated successfully, but these errors were encountered: