Search results

I am aware of what /MT and /MD means. I am asking to know which one should be for compatibility with other libraries, given that /MD and /MT libraries can't be mixed. As for the choice itself, it doesn't really matter. Almost all programs already require VC redist, so chances are that it's...

I will see what can done for laying the astronaut when dead. As for the station attachment point, adding more than one will have a considerable performance hit, so for now, there will be only one attachment point. vslAstrInfo.airlocks.at(INDEX).open = true; As simple as that. For toggle...

A question for everyone: Should I compile UACS with /MT instead of /MD? I am mainly concerned about compatibility with other libraries.

You can't scroll through airlocks in the nearest HUD mode. If you want to scroll, go to the vessel information mode. If you can make a good 3D cockpit, I would be very happy to include it with UACS. I will add an option to hide astronaut mesh when inside the cockpit in the next release. I...

Thanks for your comments! I believe I am very close to the first release. I am only waiting to see if there are more bugs before releasing. No new features are planned for the first release. 3D cockpit is too much work for me, I hardly have any experience with 3D design, and that's why all 3D...

That's because OrbiterSound5.0 (and UACS) are built with /MD, but XRSound is built with /MT, and you can't mix those in your libraries (i.e. all libraries must either be /MD or /MT).

I can make the method get the actual nearest action area, but it will be rather expensive, which isn't good given that the method is called every frame, not a one-time call. So the solution is to make all airlocks in a single vessel. I am not sure if the performance tradeoff worths the benefit...

That's because the nearest action area (and airlock) logic gets the nearest vessel first, then it returns the nearest action area in it. This will not always yield the actual nearest action area, because it's possible that an action area in a far vessel is nearer than an action area in the...

What do you mean by "I can't exit a guy"? What's the result of the call to EgressAstronaut method? Yes, you have the methods in the correct area, but there is a bug in UACS currently, so you need to call them after adding the astronaut. I am not sure what you are trying to do with the action...

What's the error message you have when you try to exit the vessel? You can't create unpacked cargoes. What you can do is create a cargo with unpackable type and unpackable only flag, add the cargo to the scenario, and unpack it. It will stay unpacked and can't be packed again. Yes, the issue...

There are 2 airlock positions: space position (pos) and ground position (gndInfo.pos). Only one position is used depending on the vessel status. So no, the egress position is always the same as the airlock position. I am not sure what you mean with the airlock size. The airlock has an ingress...

No. It searches in the list of UACS cargoes in the scenario.

There is no issue with your code. The issue is that the API should call clbkGeneric after astronaut addition, but I forgot to do so. Until the next update, just call SetEmptyMass and SetStationMesh in the same way as the ASTR_INGRS block after adding the astronaut. No. Only UACS modules can be...

Have you called SetStationMesh after adding the astronaut? After adding an astronaut, you should call SetEmptyMass and SetStationMesh to update the vessel mass and set the astronaut mesh. Same after egressing and deleting an astronaut. EDIT: Looking back, it seems like I forgot to make the API...

Currently, the astronaut always egresses with the suit on, regardless of the suit status at ingress. I will make the suit on at astronaut creation only if in unbreathable area in the next update.

Check the attached patch. It corrects the distance display on the HUD.

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.