Acetylcholine
-
Posts
14 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Posts posted by Acetylcholine
-
-
There seems to be some issues with this mod and Transfer Window Planner and SCANsat. Whenever I attempt to calculate a transfer with with Laythe (Where I set my KSC) to another of Jool's moons, the plot it gives is completely blank (Like so). As for SCANsat, I can only view maps for Jool and its moons sans Laythe. As far as I know, the SCANsat issue is not a result of user error, but I may be wrong.
-
Has an update for the current version been jerry rigged for this? Alternatively: What needs to be updated for this mod to work with the current version?
-
1 minute ago, Rhedd said:
That would be a solution. I play another game where all mods are version locked, but it's a simple process of opening the mod's config file and changing one number. Works almost every time.
Still, I think a warning message like all of my other mods give would be sufficient. Willfully stupid people be damned!
Sadly I don't think it's an issue of ignorance as much as it is of a... lack of experience in life?
A lot of these types who makes those sorts of posts strike me as being pretty young, so I don't really want to sound too harsh when I talk about them. -
1 minute ago, Rhedd said:
Not to sound TOO rude, but if a mod creator goes to the trouble of intentionally version locking a mod that would almost certainly still work after a tiny incremental update, then they have a responsibility to update it IMMEDIATELY if there are no necessary changes.
I'm not hurrying them, mind, I'm actually in favor of treating us like adults and removing the stupid version lock!
(The above was written in annoyance after finding that Kopernicus is the only mod out of my HUGE collection that I have yet noticed a problem with after updating to 1.21)
It's kind of a damned if you do, damned if you don't scenario. The current situation is mildly frustrating to everybody involved. The alternative would be frustrating to everybody involved in that it would likely cause the thread to be inundated with impatient people who fundamentally do not understand how mods work complaining about it not working ("I know the thread says the version isn't up to date, but I downloaded it on CKAN and nothing even works, why????")
Though, from poking around in the files myself, I wish it was easier to manually change the version lock related stuff, to work as a filter preventing the type of comment mentioned above, and to not completely screw over those who understand that things could very well get broken by letting the mod get loaded. -
2 minutes ago, Sigma88 said:
just out of curiosity, why are you trying to revive that mod? it has been dead for ages now, and for good reasons
Because I'm an idiot and I mixed up what tab I downloaded a link from. I think that solves the issue, that successfully pointed out to me that I had the incorrect OPM enhancement mod, though.
-
I've been attempting to bootstrap a mod into working for 1.2, and the very first issue I've noticed is related to a modulemanager cfg. Modulemanager mentioned a list of errors from a specific cfg, and within the game's logs, every single error is of the same type - "Cannot parse variable search when editing key Cloudspack =" and then the filepath for what it was attempting to edit at the time.
So I've looked into the cfg, and it's relatively simple. It goes as follows:
Spoiler@CLOUD_LAYER_PACK:HAS[#CloudsPack[*],#OPMClouds[*]]
{
@CloudsPack -= #$@CLOUD_LAYER_PACK[MainCloudsPack]/CloudsPack$
}
@CLOUD_LAYER_PACK:HAS[~CloudsPack[0],#OPMClouds[*]]
{
!CLOUD_LAYER,* {}
}
It seems that the error is occuring with the first case given - I can't say I understand fully what is going on (I am a bit ambiguous as to what "HAS" means, but I'm assuming it's some sort of conditional), I'm thinking that's the case since in all of the circumstances where the logs mentioned the second part being activated, there were no errors.
Can anybody provide any insight/advice? -
51 minutes ago, CaptRobau said:
Stock KSP now has similar functionality. Press Alt-F12. In the Cheats tab you can set the orbit now. It was introduced in 1.2
I think three people is enough to warrant me reporting this to the HyperEdit devs.
I've confirmed that it was HyperEdit causing the issues.
-
Just now, CaptRobau said:
Do you have HyperEdit installed. I've been getting similar issues and I've tried loading the game with and without HyperEdit installed and it seems that without it I don't get that issue but with it I do. Could try with and without HyperEdit?
I do. It's worth trying without it, though it would take a bit of fiddling in sandbox. I could report back on that momentarily.
-
I've been experiencing a strange problem with some OPM bodies, at the very least, Eeloo and Hale, but I feel that I've noticed it in a few other places - I'll amend this if I notice more. At certain distances, they assume an incredibly blocky look as pictured. Is this the aforementioned ugly normal map issue?
Edit: I found it in a few more places, so I'll just include where I've seen it so far as follows:
Eeloo
Hale
Priax
Tal has a strange issue.
Karen -
9 hours ago, allista said:
You're right, it is the CPS, and no, there's no currently any way to disable it (I'll make a switch for that). But it only works when a horizontal speed control is in use. So: Stop, Level (internally it's the same module as Stop; yea, I know
), Cruise and any higher-level autopilots. But, if you go manual (like @FirroSeranel proposed), leaving only the VTOL Mode, it should work.
Well, there's only one keybinding that toggles TCA, and sure, it is changeable in "advanced" pane. Push the "Change TCA hotkey" button, then push a button you which.
Thank you for your reply. Would CPS also explain the behavior I was encountering in the second post, too? In that one I was attempting to use @FirroSeranel's suggestion, using manual vertical velocity control, but I think I also had VTOL Assist on too.
I'm just trying to understand all of the nuances of this system such that I can apply it to my own (convoluted) designs. -
5 minutes ago, FirroSeranel said:
Well, what it's actually doing is looking for flat, clear terrain to use as a viable landing site. I don't think there's any way to disable that. You might have to land it manually. Try using VTOL Mode and Anchor, with normal vertical speed control. In VSC, the throttle keys increase or decrease the vertical speed set point instead, so you can make very fine adjustments, very quickly.
I was attempting to use the cruise function at the time. Using autothrottle for velocity control did make it slightly easier; however, there was still a system that made it feel like I was attempting to force two magnets together due the fact that it would direct me away whenever I got close.
-
Is there a way to disable the collision prevention system? I've been attempting to use the autopilot to land a ship on top of another vessel I made, and what I'm assuming to be the CPS keeps kicking in and shoots me away from the ship whenever I get close.
-
So, I've recently attempted to install this mod and have been having some difficulties. I can't find any information related to whether or not command parts have TCA functionality, and there is no evidence of TCA in the applications bar, VAB, or KSPedia. However, it does show the modules within the research tree.
I have performed multiple tests, both in career and sandbox, and have now reduced the contents of my gamedata folder to:
Squad
000_AT_Utils
ThrottleControlledAvionics
ModuleManager.2.7.2.dll
and have been still encountering this same issue.
Addendum:
Disregard, had the incorrect version installed.
), Cruise and any higher-level autopilots. But, if you go manual (like 
[1.3.x] [No Longer Supported Here] Alien Space Programs 1.0 - Take KSC And Push It Somewhere Else!
in KSP1 Mod Releases
Posted · Edited by Acetylcholine
@Gordon Fecyk Thank you for your response. I had actually forgotten that I was using your fork, and not the main. As it stands, I have already been using the version of Kopernicus you recommended. Is there any insight on the SCANsat issues, or should I bring the issue up to the developer for that mod instead?