liquidhype

Open Blender, look on the right hand side and click on the Scene button (2 buttons to the right of the little camera icon). There is a drop-down menu called "Units. Under "Units" it should be highlighted as "None" by default, so set that to "Metric". Now press "N" and you'll get useful information like your location transforms, rotation, scale and dimensions.

Going off of the stock sizes, a 1.875m version of the FLT-200 fuel tank (or whatever the silly stock name for it is) would be 3.04 meters tall. The FLT-200 tank in its 1.25m diameter size is 2.027m meters tall. If you import the KSP models into Blender, you need to remember that those are made in the "Blender size 1, size 2, size 3" system, meaning they are modeled in Blender units and not in metric. So If you modeled a "size 1" tank, you would need to scale it by 1.25, 1.25, 1.25 in the config file to make it appear 1.25 meters in the game. EDIT- If you use Blender, I would suggest setting your units to "Metric" and just use "scale = 1" in the .cfg file and use "rescaleFactor" to resize it if needed.

Wait, so we're supposed to just give you a bunch of models and textures? May I ask why? You said in your other post that you knew how to mod and it was "easy enough", yet you don't even seem to know how to open a texture file (for some reason you are trying to open a texture map in MS Paint). How can anyone be comfortable giving you anything, and like Cobalt asked, what exactly are you contributing?

Anyone who is still having issues with the game only going fullscreen on your secondary monitor, just delete "Kerbal Space Program" and "KSPLauncher" in the registry and everything should be back to normal. At least that fixed the issue for me. If you are on Windows 10, search for "regedit" in the search thingy on the bottom of your screen. That will open the registry. Click on "SOFTWARE" in the drop-down-meny, scroll down to "Squad" and delete the "Kerbal Space Program" and "KSPLauncher" folders. Thank you @sal_vager, appreciate the help

Sure, as long as it only affects KSP and doesn't give my PC a heart attack, I'm fine with deleting it. So am I supposed to just delete the "Squad" folder in the registry then? Or just the "Kerbal Space Program" and "KSPLauncher" sub folders? This is what I am looking at:

KSP 1.2 most likely caused this to happen, because everyone is reporting the same series of events that happened before the issue occured. As far as I am aware, no one has reported this issue in the past. I certainly did not have this issue in the previous opt-in pre-release. At this point I can only assuse that 1.2 caused peoples PCs to make some sort of new persistent file somewhere on their PCs which forces 1.1.3 onto the wrong monitor and somehow locks the resolution to (in my case) 1280x768 or lower. Surely someone on the dev team is a computer wizz and knows how to fix this.

Yea it is beyond frustrating. I must say I am surprised that not more developers have tried to solve this issue, as there seems to be quite a lot of us who are experiencing the same thing. The symptoms are all the same, we had 1.1.3 installed, opted in for 1.2, played 1.2, went back to 1.1.3 and now the game that we paid for is close to unplayable.

Correct. I've tried all the usual solutions for this issue, none of them worked. If you have a spare laptop or PC with windows 10 and don't mind being subjected to this, it is rather simple to reproduce. - Use Windoes 10 with 2 or more monitors - Have 1.1.3 Installed - Rename 1.1.3 folder from "Kerbal Space Program" to something else - Opt-in for 1.2 and let it download - Start 1.2 - Close 1.2 - Start 1.1.3 This is exactly how it happened to me. I opted in for 1.2 yesterday just to try out the new features, played for a few hours and then went back to 1.1.3. As soon as 1.1.3 was running it went into windowed mode, I went into the KSP settings and checked "Fullscreen" and then the game jumped to my secondary monitor and has resided there ever since.

It did not work for me when I tried it earlier. I even set my other two monitors as primary to test, and then set the one I want to use as primary and it did not work either. The game still only opens in fullscreen on the one monitor and it drops the resolution way down and will not let me up the res at all. I even tried uninstalling KSP, deleting all traces of the game and then re-installed only 1.1.3 and the game is still running on the wrong monitor. I even went so far as to moving all other KSP installs to a portable hard drive and left only the newly downloaded 1.1.3 on my PC. I do not understand what is causing this and it is beyond frustrating. I can deal with the game running on the wrong monitor, but I can not deal with the game running on the low resolution it is forcing me to play on.

Yea I am not going to mess around with something I do not understand. I do appreciate you trying to help though. I'll keep my eyes on the threads regarding this issue for possible solutions. Until such time, I guess I won't be playing KSP. Real bummer.

I happen to be using Windows. Looking at the registry I have the following: (Standard) Screenmanager Is Fullscreen mode_LotsOfNumbers Screenmanager Resolution Height_LotsOfNumbers ScreenManager Resolution Width_LotsOfNumbers UnityGraphicsQuality_LotsOfNumbers UnitySelectMonitor_LotsOf Number I assume that "UnitySelectMonitor" is the one I want? In any case, its value is set to "0" by default. Which value do I need and how do I go about checking if the changes worked? I have never touched the registry before, so I don't want to mess things up.

Right, so I'm not the only one having this issue. I guess that is kind of reassuring(?). The symptoms are the same on my end. I opted in for 1.2, played it for a couple of hours, then went back to 1.1.3 (which is in a separate folder elsewhere on my SSD), launched 1.1.3 and the game started in fullscreen on the wrong monitor in a much lower resolution than I normally run it on. Now I can't change the resolution and I can not for the life of me get the game to play in fullscreen on my primary monitor. It is rather frustrating as I am addicted to playing the game with about 2.5 tonnes of mods and I kind of don't want to be forced to play an unmodded game whilst waiting for full release of 1.2 and the 1-2 weeks of waiting for all the mods I use to be updated. Seeing as quite a few people are having this issue, it would be greatly appreciated of someone could create a sticky with the solution to this problem if there is one.

So are we finally getting full PBR support without having to create annoyin workarounds? Also, didn't they say they were going to redo models and textures for 1.2? Don't get me wrong, I am absolutely excited for what 1.2 has to offer, I am only asking because I recall the devs talking about somewhat revamped models and textures for the in-game parts in 1.2.

It's the interstage pusher-rod that literally pushes on the nozzle manifold in order to increase the separation distance between the upper stage and first stage for a quicker 1st stage boostback procedure. I spent a lot of time reading about it the other day. Interesting stuff actually.

If your animations work in Blender, then just drag and drop the .blend file straight into Unity. It will save you a lot of headache. The animation should work just fine without needing to do anything. Just set the thing to "Legacy", set the keyframes, give the animation a name and you are good to go.

Blender is very easy to learn and has tons and tons of tips, tricks and tutorials on the internet. I suggest you search for a beginners tutorial on Blender on either YouTube (video tutorial) or on Google (text and img tutorial). Once you have a basic understanding of how Blender works, it is as easy as going on Google and typing "how to ....... in Blender" and you will get dozens of pages showing you exactly what you need to do. KSP does not require any specific 3D modeling skills in order to make part mods for the game. All you need to know is how to make basic shapes from cubes, cylinders, planes, etc, you can make pretty much any part for KSP. I mean, most parts in KSP are cylindrical in shape anyways. Spend a couple hours watching Blender tutorial videos and do a bit of reading and I promise you, you'll have your own 3D models in no time.

What made me laugh the absolute hardest was when he was talking about the stage 2 camera placement, and he uses the engine section of a Falcon 1 to demonstrate it. This dude clearly does not know what he is talking about.

Wow indeed. The version I am using has worked up until this point, and Github did not specify v.4 so I figured I was all up to date. I assume the master download on Git is the new version then? Thank you

Is there a new version of this that I am not aware of? I accidentally deleted a few files thinking I did not need them anymore and then went on to emptying my recycle bin (yes I am a freakin' genius). I do however have these models as .mu files, but for some reason Blender won't let me import .mu files that has been exported using U5. EDIT: Forgot to mention the error that pops up when trying to import any of my .mu files. "Unrecognized format: 76543 4"

I guess it is a mix between how ULA first introduced Vulcan and people liking the look of the AJ60s more. I've been using the Vulcan a bunch the last couple of day for testing purposes, and I must say I am on #TeamAJ60 as well Vulcan looks really "clunky" with 6 GEM63XLs. But with that said, the 3.81m core Vulcan looks pretty cool with a couple of GEM63XLs strapped to it. And yes, Vulcan is going to have 3.81m core if it ever flies with the AR-1 engine because of the dense RP1 fuel. The methaLOX core will initially be a 5m core, but expanded to a 5.4m core once they start flying ACES, as ACES is going to be a 212 inch diameter upper stage.

Sweet! I appreciate the help good sir. Glad you managed to have some fun whilst testing things. Btw, I saw Tory Bruno responded to your tweet regarding these images. Cool stuff my man, cool stuff. Also, I'll get the bugs you reported sorted out and send you a new test download. EDIT: On a sidenote, I found it funny that you chose to use the AJ60s and not the GEM63XLs

If you mean "have a wack" as in you want to try to do it, then no. If you mean "have a wack" as in you know how to do it and you want to do it, then yes I would prefer someone who knows how to do it and have done it before, rather than someone attempting to do it for the first time.

I will not provide any stock support, simply because modeling, texturing, Unity and configuring all of these launch vehicles takes up too much of my time as it is.. My focus will solely be on RSS/RealFuels compability and RSS/RO compability. However, if anyone does rebalance any of the launch vehicle packs for the stock solar system (or any of the 3.2x, 6.4x sclaes), I'll will of course gladly add those files as separate downloads.

Yup, it's going to be a lot of work, but it is going to make the parts look so much better.

Thanks, appreciate it Yea I spent quite some time on deciding how to go about texturing the core tank, and I'm quite happy with how it came out. I got it to look as realisic as is possible with the current KSP shaders. I'll go over the textures once more and make them look even more realistic once KSP 1.2 hits and we get fully use PBR shaders.