Sput42
-
Posts
72 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Bug Reports
Posts posted by Sput42
-
-
So, RSS has been updated for 1.0.2. The new KSPRC is getting closer...
-
it is?
Hmm. I always thought non military, small single engine jet aircraft landed at about that speed.
Assuming neutral conditions. No head, tail, or crosswinds.
now fighter jets might typically land at higher speeds? Like an F16? Maybe because it's a little heavier.
So what speed would you say is typical for landing if not 90-100 mph? 150? 180?
So something tiny like a Learjet 45, while technically not a single-engine craft, has a final approach speed of around 140 kn (160 mph). I was hard-pressed to find anything jet-powered that approaches much more slowly. An F-16 comes in at around the same speed; even large commercial airliners tend to come in at around 130-150 kts. A standard glider plane approaches at maybe 70 kts (80 mph).
Spoilers/flaps are very much required to bring you down from that speed at any reasonable distance. Spoilers are not so much for "braking" per se; they're for killing lift so you can flare (pitch up without gaining height), which then slows you down due to increased drag. Flaps, on the other hand, alter your aerodynamics in a way that both drag and angle of attack increase, while stalling speed decreases; this means that you can flare much harder, thus slow down quickly.
Modern, small jet planes like Learjet or F-16 typically have a glide ratio of about 16:1. This means with engines shutoff, such a plane manages to glide for 800 m from an approach height of 50 m without slowing down if not using spoilers or flaps. You can probably imagine what happens if you try to slow down solely by pitching up (without going into a climb) - you run out of runway pretty fast.
There's virtually no reason for the KSC runway being long enough to land a plane without spoilers with realistic aerodynamics.
-
Ladies and gents... Get Linux. Just do it. My game idles at 6gb of ram usage. 32,000 MM pathches. And it does not, no matter how hard I try crash. The game has never hard crashed on me. It's incredible. I cannot wait for this Proot don't be scared to release a high quality version with higher res textures or something if you like in the future. Because Linux and my 16gb of ram will eat it up.
Just get it. Took me one good day to get Ubuntu up and running on a dual boot. Should've done it years ago.
Do it. Everyone. So Proot doesn't have to hear every other person complain there game is crashing with KSPRC installed.
Exactly this. I think I've experienced a single crash of KSP in a year, and that might have been due to whatever. The 64 bit version on Linux is rockstable.
The biggest danger of going that route is that you may actually find you like Linux in general and don't go back to Windows as often as you think you'd do
-
hahaha no not a toaster... not quite sure why you're calling me deluded...
yes the game needs to be optimized, and the fact that it isn't means that packs like this will inevitably have a larger hit on performance for computers without great specs (mine aren't terrible, but they aren't great for ksp, running a lowish clock quadcore processor) and considering 64 bit is not a thing and will not be until after 1.1 outside of Linux it is rather easy to run out of memory. In fact if I try to run KSP with EVE (not the low res one, that works fine) then the game crashes while loading, considering this makes use of EVE and more I somehow think my computer would struggle a bit yes, I'll just have to do what I'm doing at the moment and pick and choose enough of bits from the pack that make the game look beautiful without taking so much that I end up with crashes or low framerates, until I upgrade my PC and can enjoy the full awesomeness of this beautiful pack
Well, usually the reason for performance problems in KSP isn't the GPU, it's the CPU due to single-threaded physics calculations. All those pretty shaders and visual effects should not make your GPU scream at all.
RAM usage is a different beast, as of course all those fancy textures will take their toll, however a better computer won't help you there as long as you're limited to 32 bit on Windows. It may rather be worth it to install Linux alongside your main OS and then play the 64 bit version of KSP without ever having to worry again about running out of RAM...
-
I... this... uhm... whoa. Proot, there's no words to express what I feel when seeing the work of you and the other beautification guys. Cannot wait until this is all released and working properly, so we can bask in the beauty of the Kerbol system.
You guys rock!
-
Seems like the craft file was built when I had SetiCtt installed which made some parts physicsless. After I uninstalled SetiCtt, while still having the craft loaded on the launchpad, it still lags.
Seems like the craft file also loads the parts physicsless even when the original part is not overidden anymore in the game.
I tried a stock sandbox mode and the error messages are gone.
So I ran into the same issue (massless parts causing nullpointer exceptions in DRE), caused by SETIctt, well, making some parts (thermometers, barometers, struts, fuel pipes) massless.
Can/should this be fixed in DRE? I mean, I can mod some mass back into those parts (and I can confirm that this fixes the issue), but that doesn't sound like the cleanest solution
I'm not sure if DRE should simply ignore those parts or assign some sensible default set of thermal properties, but it should at least handle that case.- - - Updated - - -
It works nowHowever, after putting some science parts onto the ship I'm building, it's now spewing this:
(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)
[DeadlyReentry.ModuleAeroReentry] sensorBarometer: PartThermalData is NULL!
(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)
[DeadlyReentry.ModuleAeroReentry] sensorThermometer: PartThermalData is NULL!
(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)
[DeadlyReentry.ModuleAeroReentry] sensorBarometer: PartThermalData is NULL!
(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)
[DeadlyReentry.ModuleAeroReentry] sensorThermometer: PartThermalData is NULL!
(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)
[DeadlyReentry.ModuleAeroReentry] sensorBarometer: PartThermalData is NULL!
(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)
My FPS also dropped by 10 frames due to this (I think).
Log file:
https://drive.google.com/file/d/0B-Ygs3rUb405UzVuZHVESlFlQlk/view?usp=sharing
For reference, this is the original report including logs.
-
The current version of SETIctt does not play well with the new Deadly Reentry. The reason is that it sets some parts (specifically themometers, barometers, struts and fuel pipes) to be massless, and DRE really hates that. The result is tons of nullpointer exceptions in the log and a significant framerate drop.
I manually edited some low mass into SETIctt/MM-PartModding/SETI-PartMod-SQUAD-Science.cfg, and things work properly again.
-
I can't seem to be able to take data with a scientist on EVA from several US experiments (tried Mystery Goo and the Science Jr so far); the menu option doesn't show up even if I'm very close. I can take data from the Orbital Telescope US wedge, however.
Is this intended behavior? Couldn't find any reports about that on the past few pages nor in the FAQ.
EDIT: Seems like the SETI Tech Tree actually changes the dataIsCollectable property for some of the experiments for balancing reasons. I wasn't even aware that property existed, as I have never encountered a non-collectable experiment before; and I've only very recently installed SETI. So this is not a bug of DMagic after all!
-
Where did this rumour of me giving up on the mod even originate from? Of course I'm not going to kill the mod, that'd be silly, but it'd definitely help if people could read the thread, or even in some cases try the mod before they start complaining about something they saw on a screenshot.
I think it was this sentence you posted a couple days ago: "Alright, that's it, remove the sticky, we're done here." Apparently it related to a post that was subsequently deleted, so the context was gone. Scared me too for a second.
Honestly, the work you guys (blackrack, rbray, Proot, shaw, and all the others involved in those efforts) do for making KSP insanely beautiful cannot be appreciated enough. It's also very nice to see how you all cooperate across your various mods to provide a consistent experience for all of us. I'm patiently waiting for things to be released for us to test and enjoy, and I sincerely hope that you all don't get too put off by all the hype and impatient people (and bluntly, people who don't know what "wip" means and how free software communities work). I'd rather the moderators rule with iron fists in your dev threads, or close the threads down until there is a release, than any of you getting frustrated and burning out because of unwarranted pressure put on you by some people.
Please take your time and keep enjoying what you do, and rest assured that there are many people like myself that are insanely grateful for everything you give to us, whenever it may come. Thank you!
-
Having an issue on Linux x64. Completely stock, fresh install. Cant attach any heatshields to anything it seems. With some work with the mouse i can get the parts to flash green, but its difficult.
I can reproduce this, by fiddling with the mouse I can get the part to flash green for a fraction of a second immediately before it "unsticks" and jumps away from the pod, but not long enough to issue a click. Tried all sorts of things, camera angles, zooming in and out, no dice. Tried with the Mk1 pod and the DRE heat shield.
In the end I got it to attach by first attaching it upside-down to some other part, adding the pod, changing the root and removing the superfluous parts, but that's rather awkward...
-
Both Alt+F10 and Alt+F11 shortcuts seem to collide with those of other mods, thus I can't access Scatterer's settings currently. Any way to configure those shortcuts, or have access to the settings through some UI button in the future?
-
Ah, it's the old "name my first born after you" strategy...
Well I DL's the .014 (.14, whatever) and replaced the files in the folder mentioned (and only replaced files that diddn't have PQS in the filename. That fixed the pink issue. Turning off anisotropic filtering did the trick on the ground with the lines (grid lines?). But it made Kerbin from orbit look like an old CRT monitor display (alternating light & dark horizontal lines) as well as weird effects that look like irregularly shaped concentric rings centered around the focus of your POV.
Yeah, I have the same issue. Setting render quality to "fastest" didn't help either. Running on Linux, so I have no choice but using OpenGL...
-
It's right there in the first post...
-
I have noticed a problem with this mod and RoverDude's Sounding Rockets mod: sounding rockets cause a continuous metal screeching sound while in the air, and the fairings fitting sounding rockets cause sparks to appear when ejected.
-
Just a quick question, have you found/corrected the inability to complete contracts like first launch?
Or just as possible, have you determined if it is caused by interaction with another mod and not directly by FASA? (if so, do you know what it is interacting with?)
Just asking as the problem seemed to only effect (affect?) a few people on career mode and no mention on the last few pages. I haven't tried it since you first did the quick 'n dirty update to get it working with 1.0. I uninstalled it to get past those milestones, and have been following this thread since.
Good luck slaying the flying launch pad dragon. I hated the old stock launch tower, but yours are just so damn elegant!
Unrelated to FASA, which I haven't installed (yet); had this problem and could track it down to the SAS Reset mod. Removing that one allowed me to finish the First Launch contract.
Of course, if more people have that issue and they're not using SAS Reset, it may be totally unrelated to a particular mod...
-
So I had the problem that I could not complete the very early "launch our first vessel" contract in career mode, and after much widdling through my mod list I could reliably track the issue down to the SAS Reset module. If that's installed, that contract never gets completed. No clue how that could happen, but somehow it seems to interfere... didn't notice any other problems, but I also didn't have much time playing 1.0 yet.
It's certainly not a biggie, but it can be quite irritating especially since the contract cannot be canceled, and it will respawn if you remove it through savegame editing.
To reproduce, simply start a new career, accept the "first launch" contract, go to the VAB, take pod and booster and launch. With SAS Reset installed, the contract should stay incompleted.
-
Pretty cool stuff. However, one thing popped into my mind - as you're using native C++ code for much of it, did you consider portability? Will your mod run in Linux versions of KSP?
-
Is there any way to disable RSS mode in DRE, by changing configs or choosing appropriate settings?
I don't use RSS as such, but I have the stripped-down plugin installed that comes with KSPRC. It's purely used for some visual effects, the rest of the RSS stuff is not in use, however since the DLL is there, it probably gets detected as installed. I don't seem to be able to get things to explode, and suspect this to be the culprit. Tried Hard mode with the 1.12 exponent to no avail. I would assume that a stage even going down engine-first at 2800 km/s shouldn't survive completely unscathed... temperature of the engine rises to around 1600C, but nothing else happens.
-
I got it to work in 0.90 without any issues (insofar I've noticed, at least):
First, I installed the 0.90 versions (if available; I installed EVE for 0.25) of all the dependencies listed in the OP into a fresh checkout of KSP. Then I unzipped and merged the appropriate folders from the KSPRC archive. However, I made sure that I did *not* overwrite any of the other mods' .dll or .version files, and I also left KSP's own sharedasset files intact! So this step requires some care and manual confirmation for the files that KSPRC wants to overwrite (it's not that many, most of the stuff drops neatly next to the existing mods without harming anything).
The other day TextureReplacer did a new release that ships less files than the previous ones, so here you also have to make sure that you don't copy any of the stuff from the PluginData folder KSPRC ships in its bundled TR version, in addition of skipping the .dll.
That was about all I did. I'm not sure what kinds of stuff is missing considering I didn't install KSPRC's sharedasset files, but I didn't notice anything glaring. Also, surprisingly even the CityLights look correct - some people had complained that the lights are offset from the coastlines in 0.90, but I can't confirm that for my install.
I do have DDSLoader installed, but I have no clue if I have to do anything for it to work, or if it does its thing out of the box.
-
I think CKAN can't overwrite files, which would be an issue for KSPRC as it modified not only other mods, but also the game's own asset files...
-
That GTX 970 that arrived in my computer yesterday is waiting.
[1.1.2] KSPRC - Renaissance Compilation: artworks remake [V-0.7 Pre Release 3]
in KSP1 Mod Releases
Posted · Edited by Sput42
Ah yes, I got slightly confused by the fact that RSS also already switched to Kopernicus, and since they seem to have an 1.0.2 version ready, Kopernicus should be more or less ready as well
EDIT: And there it is, the Kopernicus thread has been updated!