Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

340 Excellent

About *Aqua*

  • Rank
    Rocket Scientist

Recent Profile Visitors

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

  1. A new computer. ^^ I'm done with my broken one. Only am month ago I had to replace the psu because the old didn't work anymore. The system has so many quirks and got so many temporary solutions (which became permanent solutions over time)... for me it doesn't make sense to revive it. I already had plans to buy a new computer in summer. Fortunately I just got a new job so money's rolling in. Though it'll just take a few months to save up enough. My old one: AMD Phenom II X4 955 Gigabyte something UD5 (or so) mainboard AMD Radeon HD6970 2GB 4x 2 GB RAM 3x 32 GB SSDs (differ
  2. I've got bad news. My computer just broke down. I turned it on and got a RAID error. It turned it of to check the cables and after turning it on again the screen just stays black and there's no "everything's alright"-beep. *sigh* No beeping means that the mainboard and/or the CPU doesn't work. They are almost 7 years old, there're no compatible replacement parts on the market anymore. It'll take me months to save up for a new one. Damit! Months without a computer will make me go crazy!
  3. So you're back? Ok, then I'll have a look at the new GUI and figure out how it can be done not using Asset Bundles. I've read that getting Asset Bundle GUIs and code working together only works in very simple cases. I don't know complicated it will be to get Dust working again. IIRC Visual Studio mostly complains about missing RigidBody and Renderer properties. They are moved somewhere else. But without working wheels it'll be hard to debug. I'm not sure about asking for money. I'd like to stay away from donating etc. because I fear it's going to become work inste
  4. In my local install I modified the current code to run in 1.1. If compiles without flaws (but without a lot of stuff like GUI etc.) and runs fine so far. Unfortunately the UnityEngine.WheelCollider is so bugged that there's no real hope. I attached 4 small wheels to a simple rover (I posted a picture of it before) and KSP can't decide how to orient the craft (flickers really fast between two orientations). Because of that phantom forces are added to the craft which eventually flips the craft into the air. Also driving didn't work but steering somehow created a force pushing the rover to s
  5. @nli2work Sadly the new wheel system isn't that good. For example here the wheels are somehow pressed through the runway collider (look at the main gear). I would have accepted it if they just explode if they are too stressed but clipping is a no-go IMHO. I hope Squad is still working on it. It's a pre-release so things might change again.
  6. Just click on this link: https://kiwiirc.com/client/irc.esper.net/?#kspmodders
  7. I was in #kspofficial and just came back from dinner. I'm idling in #kspmodders if you want to drop by. It's ok. I never expected to get KF running again so fast. 1.1 is only a few weeks (two?) away, so I don't mind waiting that time.
  8. I'm again in the irc for about 1 hour (might be afk for a few minutes).
  9. I don't mind. There's already a new parttools version for 1.1: http://forum.kerbalspaceprogram.com/index.php?/topic/135228-11-parttools/ This thread is also interesting: http://forum.kerbalspaceprogram.com/index.php?/topic/135442-ksp-wheel-set-up-in-unity/ But I have no idea if the KF parts are compatible with that.
  10. @lo-fi & @Gaalidas I have an hour of free time. Want to chat? I'm currently online in the official irc chat. Edit: I just set up a part cfg. The wheels start spinning when I press forward, they stop spinning when I break, they turn when I press A or D (inverted), the suspension is compressed in the editor and extended in flight, but apart from that they do nothing. That means: The rover doesn't roll or move. It just sits there. Hm...
  11. Yes, atm it is the only way to get access to it and Squad stated they won't distribute it through the Squad servers. They are to weak to handle that much traffic.The price in my country is 39.99 € . I bought the game for ~15 or 18 € back then. If you don't want to buy it, you can still have a look here: http://vehiclephysics.com/ The wheel part cfg look like this now: Edit: It seems Squad still tweaks the new wheel system. Atm it's impossible to not get into Tokyo Drift mode.
  12. We talked about that a few pages ago. The guy contacted lofi and apologized to him. The SpaceDock guys are informed and are waiting for us to pump out a new release. Then they'll delete the entry. Unfortunately it's more serious than I thought. WheelCollider seems to be completely gone. Everything is in Assembly-CSharp-firstpass.dll -> VPWheel and VPWheelCollider now. In total I counted 69(!) classes, enums and structs belonging to VP. It will take time to understand how everything is related and set up. We have to rewrite everything. *sigh* What recent te
  13. KSP 1.1 pre-release addresses some of the issues mentioned in the OP: Building Specific Subjects: Craft editor Staging diagram layering - putting the staging diagram behind the new/load/open/launch/exit bar in the craft editor. -> It works like this now. Flight screen Navball cluster - Make SAS and RCS lights click-able buttons -> They are now click-able buttons. general - Enable the movement of UI elements -> Part context menus are now movable and stay where you put them. Other UI elements are still fixed in their places. Navball markers - Sharper navball markers ->
  • Create New...