-
Notifications
You must be signed in to change notification settings - Fork 220
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
Proper Infernal Robotics integration with RP-1 (🐇🕳️) #2464
Comments
Electric props with IR parts dont work, FAR dont kount these parts "lifting" |
Even if you attach a procedural wing to them? Do helicopters not work at all in far? |
yes clayell, they just produce stupid amount of torque |
Do you think thats an IR issue or a FAR issue though? |
FAR, with this amount of torque this should already lift off |
FAR in stock treats this issue by making dlc propeller parts "un-far", so it obeys stock rules |
I wanna chime in and ask why not BG alongside IR? Either way, I think we'll need a proper robotics node, potentially offshot of the landing/rovers node. I do second this, though. |
I do not think it is worth putting time and effort to develop configs for something that people need to pay for in order to get access. (additionally, IR is better than BG in nearly every way) |
some background about KJR I think (but I'm not perfectly sure), that KJRcontinued is already compatible with IR (maybe I shouldn't say that and rather advertise my mod instead)... but, while I would love to see KJRnext as an accepted alternative for RO and RP-1, I don't want this because of the wrong reasons. There are major differences between those mods today. But let me start with some history: The mod exists mainly because KJR had no active modder during the time IRnext was first released and KJR was incompatible with IRnext. That's why I had to do something. But after digging into it more and more, I saw the potential to improve it and fix problems that KJR had back then and I started to do more for KJRnext and keep it as one of my main mods. After having done so much with joints for IRNext, I knew quite a bit about them and I saw how to solve the "drifting problem" that KJR had back then (I don't know how KJRcontinued handles this today). What I also found was, that KJR versions up to that point modified the joints in a way, that they became all unrealistically strong (and at the same time unbreakable like rubber bands) and that every version simply added additional joints like crazy. I didn't like that... because I like the challenge and every rocket bends and shakes a bit (have you ever seen the Saturn-V shake test?). But I saw, that many users of KJR wanted this. That's why I added different strength settings for KJRnext (and you can select them from the difficulty settings directly within KSP). The different options are from simply correct the unstable joints (aka "fix the problem of unity joints") up to make everything unrealistically strong (like in early/other KJR versions)... with also 2 steps between those extreme positions. I often play with the weakest settings (which is by the way also better for performance, because it does often only add 3-20 joints in my ships while the extremest setting adds 150-200 joints) and I almost never had a problem with stability except for the problems that I want... because I want that bad design break. In short again: Both KJR versions should be compatible, but they offer different flavors of the solution. |
what do you mean by that? |
FAR doesn't count lift from this kind of spinning blades from my experience
meirumeiru ***@***.***> 于 2025年2月25日周二下午8:15写道:
… Electric props with IR parts dont work, ...
what do you mean by that?
—
Reply to this email directly, view it on GitHub
<#2464 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BAXMKIE7GI2NTWLD7AESJGL2RRNHTAVCNFSM6AAAAABUFINWZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBRG43DKNZYGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
[image: meirumeiru]*meirumeiru* left a comment (KSP-RO/RP-1#2464)
<#2464 (comment)>
Electric props with IR parts dont work, ...
what do you mean by that?
—
Reply to this email directly, view it on GitHub
<#2464 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BAXMKIE7GI2NTWLD7AESJGL2RRNHTAVCNFSM6AAAAABUFINWZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBRG43DKNZYGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
ah sorry :-D I thought you're talking about 2 different things... "electric properties" and "the missing lift of those parts" ... |
By the way, if anyone wants a config for having IR parts being available in RP-1 (although not placed remotely correctly), @ionite34 made a config a while ago that I've used occasionally. (https://github.com/ionite34/InfernalRoboticsNext-RO) |
Ok, let me just start by saying that this is obviously a very long-term goal, and a very big rabbit hole. However, I would argue that having Infernal Robotics (IR), or some other form of functioning robotics system (not BG), working in RO and present in RP-1's tech tree would open up a lot of large opportunities for RP-1 missions. (and already have, for the people who have used IR in RP-1 to make some interesting mission concepts)
I'll state a few missions/ideas that are only possible with a robotics system like IR, and I know there are many more:
Custom electric-powered propeller engines (ex: Ingenuity)(according to @Not-a-flying-brick, likely not possible in-game due to FAR)Ok, saying "just integrate Infernal Robotics" is of course understating the massive amount of effort it would take to do this. Here's some things off of the top of my head that would need to be done to have IR as a well-integrated system with RP-1:
Possible Balance Problems:
Additional Notes:
This is not an easy goal, not by any means. However, I feel that it is worthy to put this issue together to try to gather some thoughts on the idea. If you have any additional ideas/problems/etc. that should be brought up, please leave them in a comment here.
The text was updated successfully, but these errors were encountered: