Jump to content

linuxgurugamer

Bug Hunter
  • Posts

    24,912
  • Joined

  • Last visited

Everything posted by linuxgurugamer

  1. If you aren't going to provide a log file, I'm not going to be able to help you. You found the problem line, but you aren't interpreting it properly.
  2. Not really. TBH, I've never used the contract, will have to put it on my list of things to look at
  3. Rather than ask for help, why not provide a log file for analysis? I can confirm it works in 1.9.1, I'm using it myself. If you aren't seeing the buttons, how do you know the game is seeing them? Also, how are you installing it? By hand or with CKAN?
  4. On one mission, I had multiple 5 1/2 hour burns. Even at timewarp, it was was still more than an hour. It was a rescue challenge, rescuing Burberry Kerman from a retrograde solar orbit.
  5. The glitches include the GetWorld3DPos not returning the correct location right after launching. There is a workaround, but I'm trying to figure out a decent solution
  6. My apologies, I left the dependencies out: New Dependencies Click Through Blocker ToolbarController
  7. They should not be negative. Nothing has changed, it may be a MM issue. I'llsee if I can look into this soon
  8. New beta release, 1.10.0.3 Fixed the issue where achievements were being lost Added more EVA achievements, one for each landable planet. Added random quotes for the additional EVA achievements Fixed bug where achievements were being dropped Added new toggle to Show all earned only Added check for duplicate keys when loading achievement while switching scenes https://github.com/linuxgurugamer/Achievements/releases/tag/1.10.0.3 Edit: I've taken the mod out of beta with this release, effective 5/25
  9. No need to change the CRP, you can add a patch to change the crp. I'll look at this PR. Tomorrow
  10. New beta release 0.1.8.1 Fixed KIS integration Available from the Github link: https://github.com/linuxgurugamer/WalkAbout/releases/tag/0.1.8.1
  11. New release, 1.10.0.2 Fixed bug where achievements were being dropped Added new toggle to Show all earned only
  12. First, wrong thread, second, ignoring the forum rules, what makes you think it doesn't work in 1.9.1?
  13. New release, 0.5.6.6 Really fixed the skin Normal Skin: Alternate skin:
  14. Did you have to quote the entire OP? In fact, it does
  15. Not a problem. There is a famous discussion about this, it's called Talking To The Bear, you can read about it here: http://wiki.greptilian.com/programming/talking-to-the-bear/ In short, explaining your problem to someone else will oftentimes let you figure out the answer.
  16. More strange data. I also dumped the rootPart.transform.position and localPosition: After initial launch: NeatherdyneMassDriver: vessel: Bug-E Buggy, GetWorldPos3D: [1086.77102203531, 592.044072977757, 1309.96491621492] NeatherdyneMassDriver: rootPart.transform.position: (1086.3, 592.9, 1309.7), localPosition: (1086.3, 592.9, 1309.7) NeatherdyneMassDriver: vessel: Bob Kerman, GetWorldPos3D: [499.578002929688, 208.686447143555, 638.983093261719] NeatherdyneMassDriver: rootPart.transform.position: (499.7, 208.7, 638.8), localPosition: (499.7, 208.7, 638.8) NeatherdyneMassDriver: vessel: m1 Ship, GetWorldPos3D: [466983.310392697, 601047.929188322, -376431.481721794] NeatherdyneMassDriver: FlightGlobals.Vessels[i].rootPart is null NeatherdyneMassDriver: vessel: M3, GetWorldPos3D: [0.44120117035064, 0.000965883546492917, -0.362673875655871] NeatherdyneMassDriver: rootPart.transform.position: (0.0, 0.0, 0.0), localPosition: (0.0, 0.0, 0.0) NeatherdyneMassDriver: vessel: M3 Ship, GetWorldPos3D: [11.8329111559249, 0.0257798374724112, -9.52662166945031] NeatherdyneMassDriver: rootPart.transform.position: (9.1, 0.0, -7.4), localPosition: (9.1, 0.0, -7.4) Stage to drop a rover, did dump: NeatherdyneMassDriver: vessel: Bug-E Buggy, GetWorldPos3D: [1120.83791006944, 591.739257621672, 1280.74852505534] NeatherdyneMassDriver: rootPart.transform.position: (1120.4, 592.6, 1280.5), localPosition: (1120.4, 592.6, 1280.5) NeatherdyneMassDriver: vessel: Bob Kerman, GetWorldPos3D: [509.252349853516, 208.381591796875, 631.922424316406] NeatherdyneMassDriver: rootPart.transform.position: (509.4, 208.4, 631.8), localPosition: (509.4, 208.4, 631.8) NeatherdyneMassDriver: vessel: m1 Ship, GetWorldPos3D: [452741.237589635, 601047.624378752, -393418.124642584] NeatherdyneMassDriver: FlightGlobals.Vessels[i].rootPart is null NeatherdyneMassDriver: vessel: M3, GetWorldPos3D: [-13.1975449720675, -0.30380933305704, 11.4401824400219] NeatherdyneMassDriver: rootPart.transform.position: (-13.6, -0.3, 11.8), localPosition: (-13.6, -0.3, 11.8) NeatherdyneMassDriver: vessel: M3 Ship, GetWorldPos3D: [-2.13696753375828, -0.278870520863944, 1.84792338724525] NeatherdyneMassDriver: rootPart.transform.position: (-4.8, -0.3, 4.1), localPosition: (-4.8, -0.3, 4.1) Now, Revert to Launch, data dump: NeatherdyneMassDriver: vessel: Bug-E Buggy, GetWorldPos3D: [1198.35686397526, 592.044047439737, 1208.78288220479] NeatherdyneMassDriver: rootPart.transform.position: (1197.9, 592.9, 1208.5), localPosition: (1197.9, 592.9, 1208.5) NeatherdyneMassDriver: vessel: Bob Kerman, GetWorldPos3D: [554.14453125, 208.686431884766, 592.339294433594] NeatherdyneMassDriver: rootPart.transform.position: (554.3, 208.7, 592.2), localPosition: (554.3, 208.7, 592.2) NeatherdyneMassDriver: vessel: m1 Ship, GetWorldPos3D: [431876.346159911, 601047.929157477, -416241.400248739] NeatherdyneMassDriver: FlightGlobals.Vessels[i].rootPart is null NeatherdyneMassDriver: vessel: M3, GetWorldPos3D: [5.14173325152179, 0.0120963886386356, -4.9437057897468] NeatherdyneMassDriver: rootPart.transform.position: (0.0, 0.0, 0.0), localPosition: (0.0, 0.0, 0.0) and after the stage: NeatherdyneMassDriver: vessel: Bug-E Buggy, GetWorldPos3D: [1198.35686397526, 592.044047439737, 1208.78288220479] NeatherdyneMassDriver: rootPart.transform.position: (1197.9, 592.9, 1208.5), localPosition: (1197.9, 592.9, 1208.5) NeatherdyneMassDriver: vessel: Bob Kerman, GetWorldPos3D: [554.14453125, 208.686431884766, 592.339294433594] NeatherdyneMassDriver: rootPart.transform.position: (554.3, 208.7, 592.2), localPosition: (554.3, 208.7, 592.2) NeatherdyneMassDriver: vessel: m1 Ship, GetWorldPos3D: [431876.346159911, 601047.929157477, -416241.400248739] NeatherdyneMassDriver: FlightGlobals.Vessels[i].rootPart is null NeatherdyneMassDriver: vessel: M3, GetWorldPos3D: [0.409642573143623, 0.000956518032801253, -0.391522816661819] NeatherdyneMassDriver: rootPart.transform.position: (0.0, 0.0, 0.0), localPosition: (0.0, 0.0, 0.0) NeatherdyneMassDriver: vessel: M3 Ship, GetWorldPos3D: [10.9532604016493, 0.0258284093342764, -10.5336008646836] NeatherdyneMassDriver: rootPart.transform.position: (8.5, 0.0, -8.1), localPosition: (8.5, 0.0, -8.1) So, things are wonky after the launch, the values change from before the staging to after. After the Revert to Launch, the values (which are different from the first set) stay the same between the pre-stage and post-stage
×
×
  • Create New...