![]() Now that I think about it, tho, since the forward windows are completley blocked anyway, you *might* be able to use a patch to rotate the IVA model a bit, to try to line up the side windows. I wont argue that it looks weird, and is a bit immersion breaking. I typically have a ship arrive, and transfer the struts to one of the station modules inventory slots, then use an engineer to go eva on that module and connect them, so all the modules possibly having diff ids makes sense to me (anyway). Bu tI leave it to you more experienced to figure out what may be occurring I think my issue is there must be many containers since each module was brought up and joined to the core of the station itself. Likely have many ID's, im assuming I have to look in persistant for this info? Modules moved top various configurations as expansion planned. Īlso wanted to add, STATION not launched all at once, modules flown up on separate launches as it was expanded. I'll try both your suggestions and see what I get. To have a permanent connection you need to take the physical strut out of the container (ID1)Īnd then first place onto the SHIP (ID2) first and then onto STATION (ID1) and it will work. SHIP has the ID of 2 therefore all parts have the ID of 2Īny Physical Struts that are placed into the container with an ID of 1 change their ID to 1. Therefore STATION has a container that has the ID of 1 STATION was launched all in one shot therefore all parts have the ID of 1 (just as an example) Sweet, beat me to it, I was working on this as well. ORBIT ORBITDISPLAY| ORBIT MAP/MAP | DOCKING | VESSEL VIEW | |ZOOM RESOURCES ST/TOT | TARGET MENU | LANDING MODE | CREW / FL.LOG | POD CAMS | EXTRA CAMS | STANDBY ![]() Here is the modified file (should be saved as: ALCORtarget60x30.txt.) I also fixed the problem with the "NO DOCKING PORT SELECTED" warning always being present (even when a docking port was selected). I modified the file ALCORtarget60x30.txt and replaced the symbols with "", "v" and "^" as a work-around. The problem was that the "/ " and "\" characters used to create the vector arrows were causing problems. I'm pleased to report that I've "fixed" the problem described above with the docking screen on the ALCORMFD60x30.
0 Comments
Leave a Reply. |