gattispilot
Addon Developer
The newest version attached works for me but not for ben. We had to fix a bug with Ummu airlock state. I recompiled and now he gets the can't find the module error
OHM The Vessels of 2001 and 2010 Patch II
- Thread starter OrbitHangar
- Start date
BenSisko
Donator
- Joined
- Feb 18, 2008
- Messages
- 420
- Reaction score
- 45
- Points
- 28
Apologies to all. The error log below was generated due to an incomplete copy of my World of 2001 v3.11 installation onto my desktop. Those .dll's were missing but I corrected that.
These are the VC++ libraries that I've installed:
VC++ 2005 redistributable
VC++ 2005 redistributable (x64)
VC++ 2008 redistributable - x86 9.0.21022
VC++ 2008 redistributable - x86 9.0.30729.6161
VC++ 2010 x64 redistributable 10.0.40219
VC++ 2010 x86 redistributable 10.0.40219
With the .dll's appropriately installed along with the above libraries, I can run this .dll
View attachment Leonov pass.zip
But not this .dll
View attachment Leonov fail.zip
This is the error log generated and the Leonov.dll IS in the Modules folder
---------------------------------------------------------------
>>> ERROR: Could not load vessel module: Leonov
>>> [Vessel::LoadModule | .\Vessel.cpp | 5442]
---------------------------------------------------------------
Thanks Face & orb :tiphat:
Code:
---------------------------------------------------------------
>>> ERROR: Could not load vessel module: LEOPOD1
>>> [Vessel::LoadModule | .\Vessel.cpp | 5442]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Could not load vessel module: LEOPOD2
>>> [Vessel::LoadModule | .\Vessel.cpp | 5442]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Could not load vessel module: LEOPOD3
>>> [Vessel::LoadModule | .\Vessel.cpp | 5442]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Could not load vessel module: YELLOWDISCOVERY
>>> [Vessel::LoadModule | .\Vessel.cpp | 5442]
---------------------------------------------------------------These are the VC++ libraries that I've installed:
VC++ 2005 redistributable
VC++ 2005 redistributable (x64)
VC++ 2008 redistributable - x86 9.0.21022
VC++ 2008 redistributable - x86 9.0.30729.6161
VC++ 2010 x64 redistributable 10.0.40219
VC++ 2010 x86 redistributable 10.0.40219
With the .dll's appropriately installed along with the above libraries, I can run this .dll
View attachment Leonov pass.zip
But not this .dll
View attachment Leonov fail.zip
This is the error log generated and the Leonov.dll IS in the Modules folder
---------------------------------------------------------------
>>> ERROR: Could not load vessel module: Leonov
>>> [Vessel::LoadModule | .\Vessel.cpp | 5442]
---------------------------------------------------------------
Thanks Face & orb :tiphat:
Last edited:
orb
New member
- Joined
- Oct 30, 2009
- Messages
- 14,019
- Reaction score
- 4
- Points
- 0
That's expected, since the module in there uses VC2013 debug libraries (i.e. it was compiled in "Debug" configuration).
gattispilot
Addon Developer
So what am I doing wrong. I am setting it to release and compiling.
Have you tried a fresh rebuild (Ctrl-Alt-F7)?
gattispilot
Addon Developer
Hopefully this one is better.
orb
New member
- Joined
- Oct 30, 2009
- Messages
- 14,019
- Reaction score
- 4
- Points
- 0
This should be fine. It doesn't require the debug versions of the VC(++)2013 libraries, but only those which are redistributable.
gattispilot
Addon Developer
Still issues:
---------------------------------------------------------------
>>> ERROR: Could not load vessel module: Leonov
>>> [Vessel::LoadModule | .\Vessel.cpp | 5442]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Could not load vessel module: Leonov
>>> [Vessel::LoadModule | .\Vessel.cpp | 5442]
---------------------------------------------------------------
jgrillo2002
Conservative Pioneer
Not sure where I would put this post but here is fine I guess. For some reason I cant move the Leonov's pods to the airlock. I have update III and applied the prior patches. I read the procedures on the book and it just wouldn't move to the airlock.
gattispilot
Addon Developer
So what happens? So have you selected the pod but the pod does move outside the ship?
jgrillo2002
Conservative Pioneer
So this is what I did. I move the pod out of its storage location, put an EVA in, rotated the pod to prepare to head to airlock. I press Ctrl 2 and nothing happens. I hear the sound but no animation
Last edited:
BenSisko
Donator
- Joined
- Feb 18, 2008
- Messages
- 420
- Reaction score
- 45
- Points
- 28
jgrillo2002,
The Leonov Pod deployment sequence is a motion sensitive event. Pod deployment can be disrupted by ship motion or relative drift between an undocked and unattached Pod and it's pad on the Leonov. To begin, make certain the Leonov is "still" i.e. no rotation or translation that can result in differential motion between the Leonov and it's pod. In the operations manual pp 47-49, it's also important to press "Ctrl+J" to detach and dock the Pod to the pad and, once the UMmu is populated to the Pod, press "Ctrl+K" to attach the Pod to the pad. This attachment is sensitive to relative motion between the ships. I'd bet this is the issue.
Hope this helps!
Ben
The Leonov Pod deployment sequence is a motion sensitive event. Pod deployment can be disrupted by ship motion or relative drift between an undocked and unattached Pod and it's pad on the Leonov. To begin, make certain the Leonov is "still" i.e. no rotation or translation that can result in differential motion between the Leonov and it's pod. In the operations manual pp 47-49, it's also important to press "Ctrl+J" to detach and dock the Pod to the pad and, once the UMmu is populated to the Pod, press "Ctrl+K" to attach the Pod to the pad. This attachment is sensitive to relative motion between the ships. I'd bet this is the issue.
Hope this helps!
Ben
jgrillo2002
Conservative Pioneer
Tried everything you said. Still a no go. I even selected Pad 3 and tried to press Ctrl 1 and it doesnt do anything. If you want Ill make a video showing the problem
Last edited:
gattispilot
Addon Developer
A video might be good. If the pod is attached does the pod rotate to the door way. I think the door needs opening and then the pod will move to the airlock area?
jgrillo2002
Conservative Pioneer
Last edited:
BenSisko
Donator
- Joined
- Feb 18, 2008
- Messages
- 420
- Reaction score
- 45
- Points
- 28
jgrillo2002,
Sorry for the delay. Thanks for the video. I haven't been able to reproduce the issue you've identified. I've used the scenarios Leonov in Earth orbit and Leonov and Discovery with TMA2 to test Pod/pad animation. In the movie, Pod 2 is used but I've tested all three. I can rotate all pods using Ctrl+1 and get them to docking position. There is a glitch in the animation though. After the Pod is populated Ctrl+2 rotates the Pod/pad to face the Pod airlock door. Keypad "5" opens the inner airlock door. This step can disrupt Pod extension. Sometimes the inner airlock doors open but closes within a few seconds. Be sure the doors open and remain open (that's the reason for the 5 sec wait) then press Ctrl+3 to move the Pod/pad into the airlock. This glitch can also disrupt Pod retraction. Unfortunately I can't reproduce the glitch you've identified. If there is another scenario please send it and I'll look again.
Ben
Sorry for the delay. Thanks for the video. I haven't been able to reproduce the issue you've identified. I've used the scenarios Leonov in Earth orbit and Leonov and Discovery with TMA2 to test Pod/pad animation. In the movie, Pod 2 is used but I've tested all three. I can rotate all pods using Ctrl+1 and get them to docking position. There is a glitch in the animation though. After the Pod is populated Ctrl+2 rotates the Pod/pad to face the Pod airlock door. Keypad "5" opens the inner airlock door. This step can disrupt Pod extension. Sometimes the inner airlock doors open but closes within a few seconds. Be sure the doors open and remain open (that's the reason for the 5 sec wait) then press Ctrl+3 to move the Pod/pad into the airlock. This glitch can also disrupt Pod retraction. Unfortunately I can't reproduce the glitch you've identified. If there is another scenario please send it and I'll look again.
Ben
Similar threads
