Hello "HUTCH"Hi Pappy
its line 1 its still calling the old spacecraft version you need to change line 1 to
its one of those things that stares you in the face
You need to install this: https://www.microsoft.com/en-us/download/details.aspx?id=40784Hello "HUTCH"
I change the line as you told me the
I now launch this error message is displayed
This application has failed to start because MSVCP120.dll not found
reinstalling the application may fix this problem "OK"
if I continued with "OK" to scenario starts but the robotic arm is not visible and using the "CTRL + SPACE" hand control is still not visible
an idea ?
Hi DaveS I tried this but still have Pappy's problem, when the V4 came out it worked great for a couple of weeks now it doesn't no visuals and no Dialog box. I tried down loading the C++ download but no good.You need to install this: https://www.microsoft.com/en-us/download/details.aspx?id=40784
Are you sure you installed the right version on the runtime package? You should install the x86 version as Orbiter is a 32-bit application and not a 64-bit application.Hi DaveS I tried this but still have Pappy's problem, when the V4 came out it worked great for a couple of weeks now it doesn't no visuals and no Dialog box. I tried down loading the C++ download but no good.
I'm running windows 8 but I also tried it on my windows 7 laptop and the same on the JemRMS as well. will go back to version 3 the Module on that works fine it seems to be where the problem is with version 4
any body got any ideas?
change ATTACHED 1:2,Destiny to ATTACHED 2:2,DestinyHello David,
OK I tried with
STATUS Orbiting Earth
RPOS 3554149.41 -1232248.07 5586388.07
RVEL -4611.803 4714.825 3962.852
AROT 82.61 2.73 -112.51
VROT 0.00 -0.05 0.04
NAVFREQ 0 0
ARM_STATUS -112.257771 -8.891015 10.359992 -102.232705 0.210458 3.645633 12.753353
FOLDED 1 1.0000
CAM_STATUS 0.000000 0.000000 0.000000 0.000000
ATTACHED_PAYLOAD Destiny 2
and everything is ok
and good flights
Hi yeah I have to use version 3 of the Canada Arm because I can't seem to get it working in windows 8 with version 3 this works finechange ATTACHED 1:2,Destiny to ATTACHED 2:2,Destiny
Hello "bekodreko"change ATTACHED 1:2,Destiny to ATTACHED 2:2,Destiny
Hi Guess what, I went in to Norton Internet Security and checked the SSRMS.dll and it says fewer than 50 people have used this software and it is considered unsafe so I clicked Trust this application and suddenly it is working perfectly again.Hi there just had Norton Internet security put up a pop up and scan the canadaram .dll in modules in my unzipped folder and it came up said that SSRMSD.dll is unsafe and has been removed.
none of my other unzipped addons has ever been scanned by Norton and removed this is very strange
I believe SiameseCat is looking at this.Any chance for an Orbiter2016 build ?
I have tested the SSRMSD in Orbiter2016 and it works BUT:
If you switch into cockpit-mode AND the HUD is on, SSRMSd.dll crashes orbiter.
So it seems to be that the HUD-overlay might causing the crashes, and it might be just a matter of re-compile against latest Orbiter SDK.
The problem is, the only sources I found are within the SSU-sources and here the SSRMS-source is pretty old.
I guess, that's the first version even without the nice controll-box.
Btw., I have had successfully converted the MBR_its-addon to vessel3.
So the HUD(power-output....angels) can be seen in D3D9-client via HUD, without the need to switch to GDI-compat-mode.
This works in Orbiter2016, too.
So if we would have the SSRMS, we would have something nice to carry and to construct.