Search results

I got it now. This value is simply the distance from the zero Y level to the astronaut feet. So if the mesh is positioned so that the astronaut feet is at zero Y, the value should be zero. Likewise, if the mesh is positioned so that the astronaut head is at zero Y, the value should be the...

I didn't get what the issue it. If you attached a photo, it didn't appear for some reason.

Action areas are very similar to airlocks. Here is a simple sample: void Vessel::clbkSetClassCaps(FILEHANDLE cfg) { UACS::ActionInfo actionInfo; actionInfo.name = "Action area"; actionInfo.pos = { 4,0,-1.3 }; vslAstrInfo.actionAreas.push_back(actionInfo); } int...

Stations are the seats for astronauts. Slots are for cargo. You can specify which airlock to egress from in the EgressAstronaut method with the airlockIdx parameter, or pass nullopt and the API will use the first one available.

New release: https://github.com/abdullah-radwan/UACS/releases/download/v1.0-prerelease6/v1.0.Pre-release.6.zip Changelog: Added Action areas. Changed Ingress range are now specified by the vessel. Renamed InBreathableArea to InBreathable. Astronauts can specify whether to check atmosphere or...

I should have something out within a month.

The PDB files contain debug information, useful for other developers to track calls and identify bugs. As for the CTD, it seems like it has nothing to do with UACS. Maybe your Orbiter installation is broken. Try a new installation and report back.

New release: https://github.com/abdullah-radwan/UACS/releases/download/v1.0-prerelease5/v1.0.Pre-release.5.zip Thanks to @Jason von Jolkos for discovering a critical bug! Changelog: Added DrawAstrInfo and DrawCargoInfo methods. Fixed GetEmptyStationIndex working in reverse, causing several...

The breathable area size is the vessel size. I have limited time available, but I will work on action areas. Thanks! You just discovered a bug. It will be fixed in the next release. You have to manage the index manually until the update is released.

Currently, no. The vessel must implement UACS C++ API in its code to support astronauts and cargoes.

New release: https://github.com/abdullah-radwan/UACS/releases/download/v1.0-prerelease4/v1.0.Pre-release.4.zip Changelog: Added Astronaut name and role on the astronaut HUD. PDB files for UACS DLL modules. Changed Station and airlock index in TransferAstronaut and EgressAstronaut method is...

I will see what to do about action areas. Maybe in the next release, maybe not...

That's the tax for making it too customizable. Anyway, the 'automatic scroll' should make things easier. Some things have to be done by the vessel though, like the animations.

I sent you an email detailing the animation part. Set the airlock open when the door is fully open, and closed when the door close command is given. As for all these scrolls, I will add an 'automatic scroll' in the next release, so you don't have to pass a station or airlock. If you didn't...

If you have the source code of it, you can make it a custom astronaut as detailed in the developer manual. Otherwise it's not possible.

As I said, the best as I see is that bases should have actual astronaut vessels, not information. In this architecture, transfers between bases and vessels isn't possible.

You can define a station index and scroll through the station using vslAstrInfo.stations vector as a reference (size method). Displaying the astronaut role is a good idea. It will be added in the next release.

Sorry if I sound aggressive. English is not my first language, and I was trying to explain how UACS is currently coded, not 'this how it is, whether you like it or not'. For transfers, a way to transfer astronauts between 2 ground vessels within a certain radius for example is possible. Let me...

It's impossible to add astronauts to a vessel that doesn't support it. Currently, there are 2 ways to add an astronaut: inside a vessel by the vessel, or directly in the scenario by scenario editor. Both vessels must be docked to transfer astronauts between them. Otherwise, you have to egress...

You can get the role by using astrInfo.role in clbkGeneric for example. Currently, it's not possible for MFDs to add astronauts because it must be added inside a vessel. MFDs however can change astronaut info. I might make an MFD which does that.