Jump to content

Jasseji

Members
  • Posts

    453
  • Joined

  • Last visited

Reputation

115 Excellent

1 Follower

Profile Information

  • About me
    Rocketeer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 3440x1440 isnt THAT big. 1080p resolutions are a thing of the Past and more and more 1440p is the go-to standard in gaming
  2. Hence i can understand some people who expected more from KSP2 EA than KSP1 EA. The argument "but KSP1 had even more bugs at the start" doesnt seem to be really valid
  3. Yes, but, how much did KSP1 EA Cost on Day 1 ?
  4. what about kerbal-friendly Interface, maybe they prefer it that way ? you Racists
  5. Exactly this, i played around with Unity a bit but before i even thought about installing it, i did simple cfg tweaks, which was some kind of "modding" for myself. So for me the "entry into modding" was to do some cfg tweaks, MM patches and then only installing Unity for trying to make parts (although i failed miserably ) If everyone has to install Unity to even consider getting into modding, then it's maybe "(pro) modder friendly" but not "start with modding - friendly"
  6. i run Call of Duty on Ultra settings with ~40fps on my RTX3070 and in 5120x1440, KSP doesnt run higher than 25fps even if i reduce to 3440x1440, so no, it doesnt "eat up resources as AAA on max" it eats up more with lower quality @VITAS is it possible to add a distinction on SpaceDock for ModLoader ? like category BePinEx and SpaceWarp ?
  7. But will it require installing Unity and packaging asset bundles each time ?
  8. it very much seems that point 3. is the biggest hurdle and might kill a big part of the Modding community - as in, a lot of modders did rely in KSP1 on people testing their mods and tweaking the cfg's to try out different options - this would mean that now everyone who wants to contribute to mod testing or bug fixing will have to install Unity which a lot people wont do , so less testers, less incentivie for modders to actually do something because they dont have the time/assets to test everything out themselves. Quick Example: 1. Part behaves strange on some trajectory 2. edit cfg to change drag/mass/whatever value 3. Rinse and repeat point 2. until 4. applies 4. Part behaves correctly 5. Issue found and adressed by the modder in next release (or if modder is unavailable, cfg tweak is posted on forum for everyone to implement if they wish) Above could be done by anyone with access to Notepad, having the need to install Unity will kill a lot of such troubleshooting Edit: i dont say that cfg's were good but they were easily accessible is what i mean
  9. i'd personally go for what @linuxgurugamer uses and recommends as he's the one with most mods on maintenance for KSP1
  10. This is your fault btw.

  11. i think that's included in BDB and somewhere benjee said he wont copy it
×
×
  • Create New...