Jump to content

Moosemint

New Members
  • Posts

    2
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

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

  1. Reported Version: v0.2.1 (latest) | Mods: UITK for KSP2, BepInEx, Micro Engineer, Manuever Node Controller, Lux's Flames and Ornaments, Noed Manager, Wayfarer's Wings, Community Fixes, Flight Plan | Can replicate without mods? Yes OS: Windows 10 | CPU: AMD Ryzen 9 300X 12-Core processor | GPU: NVIDIA GeForce RTX 2070 | RAM: 65536MB Only "Horizon Mode" camera view appears to work correctly - Celestrial camera appears to functional in the exact same way as "Horizon" does currently (Severity: Low, Frequency: High, constant without exception). No steps needed to replicate - simply begin a game, and place any vessel into orbit around any celestial body. Expected behaviours Horizon Camera view functions perfectly, placing the currently orbited celestial body "below" the active vessel. Works perfectly for launches and atmospheric flight, landings on celestial bodies, EVAs on celestial bodies, ect. Celestrial Camera View: I'm still new to KSP2, so still learning my way around. This is how I expect Celestial camera to work: the same as Orbital camera view from KSP1? Or at least, exhibit different behaviours than Horizon camera view. The camera should be orientated so all of the Kerbol System's planets are viewed on a horizontal plane, matching the same camera orientation as in the Map View. In Celestial mode (I assume), from the point of view of a vessel on a perfectly equatorial orbit, the orbited celestial body will appear to move around the vessel horizontally (as with Orbital view). However, from the point of view of a vessel on a polar orbit, the orbited celestial body will appear to move around the vessel vertically. Actual behaviours Horizon camera view appears to work perfectly, however Orbital camera and celestrial camera currently behave in the exact same way as Horizon camera does. This occures regardless of vessel orientation. This can be quite disorientating for players coming from KSP1 (such as myself) or players expecting to see the solar system orientated to match any given planet's orbits around the sun. In the attached video I demonstrate how Horizon and Celestial camera views appear to function in an identical way currently, and occasionally there are weird camera snaps when switching between camera modes - as though the camera almost behaves as expected, before reverting to copy the Horizon view. Unclear if related: Automatic camera always seems to default to "Horizon" view. Chase, Body and Capture cameras also all seem to function in the exact same way, and I haven't been able to tell them apart. Included Attachments: HorizonandCelestialCameraBug.mp4 .ipsImage { width: 900px !important; }
  2. Reported Version: v0.2.1 (latest) | Mods: UKIT for KSP2, BebInEx, Micro Engineer, Maeuver Node Controller, Node Manager, Community Fixes, Flight Plan, Lux's Flames and Ornaments, Wayfarer's Wings | Can replicate without mods? Yes OS: Windows 10 | CPU: AMD Ryzen 9 300X 12-Core processor | GPU: NVIDIA GeForce RTX 2070 | RAM: 65536MB As in the title, I've noticed that if I time warp while landed on Mun or Minmus, I will get a notification warning me that [vessel] is about to crash, after which the vessel disappers. When my pilot is on board the vessel, I can see it falls beneath the surface of the moon in question, and begins "orbiting" at between -5000 or -6000 meters. If my pilot is on EVA while I time warp, the vessel still disappears but my kerbal stays exactly where I left them. I have experienced this bug with no expections - anytime I warp, the bug occurs, I have not yet succesfully time warped while landed without experiencing the bug. Steps to replicate: Land a vessel on Mun or Minmus, and time warp. I haven't tried this on any other celestial body, including Kerbin, since the most recent update. In the attached save file, the vessel in question is "Cheesecake-12", which is landed at the Minmus Monument. It was built in the "Mission Minmus" workspace. It seperated from the command module "Cheesecake-11" which is in orbit around Minmus. Extra information (possibly unrelated). On my first experience of this bug, I EVA'd the kerbal to do some science, and quicksaved. I opened the parts manager and clicked on "collect surface sample", however she planted a flag instead. I was then unable to perform the "Crew Report" science. I then time warped and experienced the Vessel is Crashing bug, and reloaded my quicksave, however this time science collection went as expected. Included Attachments: MissionMinmus.json quicksave_29.json quicksave_28.json .ipsImage { width: 900px !important; }
×
×
  • Create New...