Skip to content
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

1.0.5 Checklist #671

Closed
13 of 18 tasks
NathanKell opened this issue Nov 12, 2015 · 11 comments
Closed
13 of 18 tasks

1.0.5 Checklist #671

NathanKell opened this issue Nov 12, 2015 · 11 comments

Comments

@NathanKell
Copy link
Member

1.0.5 adds a bunch of useful thingies relevant to our lives. I'm going to continuously update this OP as more checklist items get added (and more get checked off, one hopes). Please feel free to assign yourself, either by editing (if a collab) or by posting a comment, and a collab will edit it into the OP.

  • Adjust Physics.cfg values for RO use. Note that crossfeeding for STACK_PRI can be toggled, and the actual physics constants and FX constants need updating. @NathanKell
  • Remove RO Shroud Toggle, functionality is stock now.
  • Rebalance heat shields (again). @NathanKell (and @stratochief66 ?)
  • Revert to ModuleRCS since it basically is ModuleRCSFX now.
  • Update any DRAG_CUBE overrides - there are quite a few in stock KSP, and if we rescale parts we need to update drag cube areas and extents.
  • Remove Crossfeed Enabler
  • Add ModuleToggleCrossfeed to appropriate parts (mod decouplers? What else?)
  • Disable intakes and jets when under water (will be done by AJE, so no worries.)
  • Update all AJE-configured parts to have correct propellants (AJE no longer does this).
  • Add hypothetical configuration for the RAPIER and best-guess for the SABREs.
  • Support new parts. (Vector, Panther, Goliath, Mk1 crew cabin, Mk3 mount and ramp, maybe add the new Mk1 cockpit as a new part, and keep using Ven's old cockpit? Wut do?)

Related Mod Dependent Items

  • Coordinate with @Starwaster regarding RF boiloff, and with him and @toadicus regarding any refrigeration code.
  • Add RP-0 entry costs and technodes for all added CONFIGs for engines.

Deferred Items

  • Update docking ports to use snap angles and gendered setting.
  • Set up a proper kerbal drag cube (and, possibly, rescale kerbals?). Change kerbal RCS thrust.
  • Tune hatch obstruction check raycast distance for new part sizes.
  • Apply cylindrical and spherical solar panel mode where appropriate.
  • Use added scaling variables to rescale IVAs and the kerbals in them.
@stratochief66
Copy link
Member

Once we have Kopernicus up again, I am all up for working heatshields

@NathanKell
Copy link
Member Author

Awesome. I'll check with @ThomasKerman tomorrow.

@NathanKell
Copy link
Member Author

Not listed here, but supported the Mk3 engine mount and ramp. The other new parts still need configs.

@PhineasFreak
Copy link
Contributor

ModuleRCSFX is included with the standalone Realism Overhaul installation zip file. Shall we remove it now?

@NathanKell
Copy link
Member Author

@PhineasFreak Yeah I need to update the netkan for that. Good point.

In other news, RSS is working with dev Kopernicus! Just made my first RO orbit in 1.0.5.

@Olympic1
Copy link
Contributor

00d8e61 and fc7ffa8 break the RO release of KSP 1.0.4. It is better that you update the netkan file after the release, as this file will be checked every ~3 hours. If you could revert these commits and add them back in after the release, that would be very helpfull.

NathanKell added a commit that referenced this issue Nov 17, 2015
NathanKell added a commit that referenced this issue Nov 17, 2015
@dearmoon9
Copy link
Contributor

New 1.0.5 jet engines - P&P for RP-0

KSP-RO/RP-1#364

@NathanKell
Copy link
Member Author

Ok. As of the latest commit ( 20c0a63 ) please

consider RO in Release Candidate mode.

@dearmoon9
Copy link
Contributor

P&P for new 1.0.5 parts:
KSP-RO/RP-1#376

Update for entryCostModifiers:
KSP-RO/RP-1#377

@stratochief66
Copy link
Member

@NathanKell anything from this list that you want to keep as 'To Do's for 1.1?

Or else, close?

@NathanKell
Copy link
Member Author

All the deferred items still need to be done, but there should be a new issue made, good point. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants