OHM US ISS A to Z v.3

Thanks for the correction. funny no one noticed before this. It is actually CMG2.dll that is included.
 
For those having problems docking with the PMA2dummy I think I found a way to solve this issue: Just delete all the lines corresponding to the [DOCK_0] and [DOCK_1] in the config\spacecraft folder (PMA2dummy.ini and PMA2.ini). For me it worked fine I hope for you too :salute:
 
Last edited:
For those having problems docking with the PMA2dummy I think I found a way to solve this issue: Just delete the lines corresponding to the [DOCK_0] and [DOCK_1] in the mesh conf. files (PMA2dummy.ini and PMA2.ini). For me it worked fine I hope for you too :salute:


Are you referring to files in the config\spacecraft? also, do you mean to delete the whole thing, eg:

Code:
[DOCK_0]
;to shuttle
POS=(0,0.625,1.082)
DIR=(0,0,-1)
ROT=(0,1,0)

DOCK_1]
;to node
POS=(0.00,-0.086,-1.278)
DIR=(0,0,1)
ROT=(0,1,0)

I had a problem of my rectangles appearing at the back, leading me in through the back of iss (meaning I had to penetrate all the other modules and dock to pma2 from the inside. Is this the problem you're referring to?

Thanks
 
Are you referring to files in the config\spacecraft? also, do you mean to delete the whole thing, eg:

Code:
[DOCK_0]
;to shuttle
POS=(0,0.625,1.082)
DIR=(0,0,-1)
ROT=(0,1,0)

DOCK_1]
;to node
POS=(0.00,-0.086,-1.278)
DIR=(0,0,1)
ROT=(0,1,0)

I had a problem of my rectangles appearing at the back, leading me in through the back of iss (meaning I had to penetrate all the other modules and dock to pma2 from the inside. Is this the problem you're referring to?

Thanks

Yes! The files (PMA2dummy.ini and PMA.ini) are in the config\spacecraft and you have to delete the whole thing for proper working :yes:

The problem I was refering to was the incapability of docking to PMA2dummy (ISS AtoZ by Donamy) -You just can't dock to it, you fly all the through the PMA2-.

In the Docking MFD don't set the PMA2dummy as target because it won't work as long as you've deleted the Dock_0/Dock_1 in the config\spacecraft\PMA2.ini. and config\spacecraft\PMA2dummy.ini.. When you're in front of the docking port (PMA2) Set visual in the Docking MFD then it will guide you all the way to the contact point.

P.S.: You're not actually docking to the PMA2 but to the Harmony Module :tiphat:

-Sorry for my bad English :blush:
 
The reason you cannot dock to the PMA2, is because it is a child of the Harmony when it is attached. If you dock the PMA2 to the Harmony, then it will work. The list of things docked to everything else was too confusing, that's why I changed to attachments instead. The docking point were just never deleted.
 
The reason you cannot dock to the PMA2, is because it is a child of the Harmony when it is attached. If you dock the PMA2 to the Harmony, then it will work. The list of things docked to everything else was too confusing, that's why I changed to attachments instead. The docking point were just never deleted.

Thank you for clarifying the reason we can't dock to the PMA2 :thumbup:

I deleted the docking points on my own, because was the only way I found to solve this issue. If you know another way to make it work feel free to share it with us :tiphat:
 
Beautiful add-on. I noticed in my installation that the sun facing solar panels have no texture; they're blank white no matter what angle I view them from. The dark side of the panel (side away from the sun) looks normal:
picture.php


I also noticed that this add-on overloads OrbiterSound. I get multiple lines in OrbiterSound_Log.txt that say:
Code:
Only 60 vessel allowed
My XR vessels don't have custom sounds as a result.
 
Reinstall the addon's textures and it'll work fine.

Tried that, still get the blank solar panels. I reloaded both A2Z and Thornton's ISS 3.2. Orbiter.log excerpt:

Code:
Module SouyzTMA.dll .......... [Build 100902, API 100830]
Module Progress_M1.dll ....... [Build 100902, API 100830]
Module SouyzTM.dll ........... [Build 100902, API 100830]
Module Strela.dll ............ [Build 100904, API 100830]
Module CMG2.dll .............. [Build 110727, API 100830]
**** WARNING: Mesh not found: .\Meshes\lightpole.msh
D3D9Client::clbkStoreMeshPersistent(lightpole) hMesh is NULL
Module OTD.dll ............... [Build 100904, API 100830]
Module spotlight.dll ......... [Build 110308, API 100830]
Module evatether.dll ......... [Build 110406, API 100830]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
**** WARNING: Mesh not found: .\Meshes\.msh
**** WARNING: Mesh not found: .\Meshes\.msh
**** WARNING: Mesh not found: .\Meshes\.msh
Repeat that warning about 140 times
Code:
**** WARNING: Mesh not found: .\Meshes\.msh
D3D9Client: [Scene Initialized]
Module Train.dll ............. [Build 120629, API 100830]
Module XR5Crane.dll .......... [Build 120519, API 100830]
Module ThemLPad.dll .......... [Build 120519, API 100830]
Module RadarDish.dll ......... [Build 120519, API 100830]
Module BigPad.dll ............ [Build 120519, API 100830]
D3D9Client: [Session Closed. Scene deleted.]
SketchPad Pens still in use 8
SketchPad Brushes still in use 18
**** Closing simulation session
 
Last edited by a moderator:
make sure your PVarray.dds looks like this.
 

Attachments

  • PVarray.jpg
    PVarray.jpg
    100 KB · Views: 42
make sure your PVarray.dds looks like this.

Speaking of that texture, could you make a new version that has the weird color distortions removed from the active side? They just lower the quality of the overall texture appearance and make the SAWs look bad.
 
Speaking of that texture, could you make a new version that has the weird color distortions removed from the active side? They just lower the quality of the overall texture appearance and make the SAWs look bad.

That doesn't tell me very much. Do you have a picture that shows the 'weird' distortions ?
 
That doesn't tell me very much. Do you have a picture that shows the 'weird' distortions ?
Here. Note how the there's almost a diagonal "wave" of rainbow like distortion increasing in saturation near the right-hand end of th texture.

PVarray_modified.jpg
 
Two pictures of the arrays never look the same anyway, the light is always different. I think you're just splitting hairs.

Check this out.
 

Attachments

  • 157859main_image_feature_657_ys_full.jpg
    157859main_image_feature_657_ys_full.jpg
    268.9 KB · Views: 51
Last edited:
Yes... the waves on the solar array texture are actually on the real array caused by the array not being perfectly flat - but these patterns change over time, as the ISS maneuvers.
 
Which is a little hard to simulate in Orbiter, but the D3D9 client may help.
 
make sure your PVarray.dds looks like this.

Thanks for this. For some reason it only had the one texture in it. I had re-copied all the texture files from the zip folder before, but it didn't take somehow. I did it again now, made sure both textures were there, and now it's fine. Bonus is that a few other textures on the small parts that I didn't notice were missing before are there now too. I wonder how they got corrupted. Thanks again!
 
You may have downloaded some of the earlier payloads that I made, after the ISS AtoZ, some of the textures were probably changed in the newer version. That's all I can think of.
 
Any ideas about the Orbiter Sound limit? Should I put non-A2Z vessels before the A2Z components in the scenario files? Do any of the A2Z components have custom sounds?
 
no custom sound files. I don't use sound in space.:lol:
 
  • Hailprobe
Reactions: PDF
Back
Top