- Joined
- Feb 4, 2008
- Messages
- 9,450
- Reaction score
- 705
- Points
- 203
Yes.Do you use TortoiseSVN?
Yes.Do you use TortoiseSVN?
Yes.
Thanks, this is now done.Then just use the right mouse button and select "Branch/Tag" in the "TortoiseSVN" Menu for the whole SSU repository.
Then enter the path and name of the branch (its just a folder on the repository in the "branches" directory)
Thanks, this is now done.
Do that as that one was mistake, I forgot to add "branches\" before the "2.1-newmehses" when I created the branch.Yes, there is now a second one at the wrong place (correct one: branches/2.1-newmeshes), I'll erase it from the repository, if you don't mind.
Do that as that one was mistake, I forgot to add "branches\" before the "2.1-newmehses" when I created the branch.
Confirmed and added as an official ticket item.One item found.
This is something I cannot confirm. They rotate correctly for me.item 2 dataprobes rotate in the wrong direction.
It is for me when deploying. This is as seen from above with the nose pointing up.When looking from above the port side should rotate CW.
Mesh problem, there's tons of them. Pay them no mind as we're going with new meshes in v2.1.Also, item 3
I can't open the Orbiter mesh in MeshWizard; I get "Run-time error 9: Subscript out of range". For some reason, MeshWizard doesn't seem to like the FUSELAGE and LOX_UMBILICAL_PANEL groups; I'm not sure if this is a problem with MeshWizard or with the new mesh.Checked in the new meshes/textures into the 2.1-newmeshes branch.
---------- Post added at 01:26 AM ---------- Previous post was at 12:07 AM ----------
I decided to check in the OMS pod meshes as they're done, it's just the texture that is incomplete. So they're usable, they just don't look too good at the moment.
Let me check on these, I'll report back.I can't open the Orbiter mesh in MeshWizard; I get "Run-time error 9: Subscript out of range". For some reason, MeshWizard doesn't seem to like the FUSELAGE and LOX_UMBILICAL_PANEL groups; I'm not sure if this is a problem with MeshWizard or with the new mesh.
---------- Post added at 11:42 AM ---------- Previous post was at 11:25 AM ----------
Also, is there a reason why there are 2 groups labeled LEFT_PLBD_EXT? This isn't a problem for coding, but it seems a bit odd.
I'll take a look, it's better to fix it in the source rather than implement some workaround don't you think?The new mesh works for me too.
---------- Post added at 07:18 PM ---------- Previous post was at 04:18 PM ----------
The Ku_band_DA mesh also has 2 groups named Gimbal_lock_structure and 2 groups named Dish_receiver_supports. Again, this can be handled in code easily if you don't want to modify the mesh.