Bug (NASSP ADDON) Saturn 5 spawns at wrong position

Joined
May 8, 2011
Messages
71
Reaction score
0
Points
6
Location
Pozega, Serbia
I've got this annoying problem with Saturn V rocket (NASSP for Orbiter 2010), when I start any scenarios with S5, It puts my rocket and its launchpad away from launch site, so It's like floating on the air. How do I fix this?

Image available:
http://postimage.org/image/zwfyq77o/

Thanks in advance.
 
Last edited:

Saturn V

Addon Developer
Addon Developer
Donator
Joined
Mar 24, 2008
Messages
548
Reaction score
2
Points
0
Location
West Hell
Open the scenario, the press "F4" to bring up the drop-down menu. Select Scenario Editor - highlight the offending vessel and move it where it belongs.
 
Joined
May 8, 2011
Messages
71
Reaction score
0
Points
6
Location
Pozega, Serbia
Open the scenario, the press "F4" to bring up the drop-down menu. Select Scenario Editor - highlight the offending vessel and move it where it belongs.
When I do so, it corrupts on the launching, autopilot cancels and rocket starts wiggling outta control.
 

luki1997a

Active member
Joined
Dec 9, 2010
Messages
314
Reaction score
0
Points
31
Location
Biłgoraj
I think this bug is caused by moved KSC(in Orbiter 2006 KSC was in another place approx. 30 m. displaced) now- in 2010 KSC is in proper position, so most of add-ons designed for 2006 are spawning at wrong position for example. DGIV or as you wrote: NASSP(Saturn V). I think you can't move it by changing location because it was designed for launching from coords from O 2006.
 

IronRain

The One and Only (AFAIK)
Administrator
Moderator
News Reporter
Donator
Joined
Oct 11, 2009
Messages
3,484
Reaction score
403
Points
123
Location
Utrecht
Website
www.spaceflightnewsapi.net
When I do so, it corrupts on the launching, autopilot cancels and rocket starts wiggling outta control.

What you could try is move the desired vessel, exit orbiter and load the Current State scenario and try if that works, although I highly doubt it (for the reason mentioned by luki1997a).
 
Joined
May 8, 2011
Messages
71
Reaction score
0
Points
6
Location
Pozega, Serbia
I think this bug is caused by moved KSC(in Orbiter 2006 KSC was in another place approx. 30 m. displaced) now- in 2010 KSC is in proper position, so most of add-ons designed for 2006 are spawning at wrong position for example. DGIV or as you wrote: NASSP(Saturn V). I think you can't move it by changing location because it was designed for launching from coords from O 2006.

I don't think so, there are other addons which have the same problem, and I don't know how to fix it. BTW, I'm using NASSP for Orbiter 2010 which it was made for so there shouldnt be any probs.
 

IronRain

The One and Only (AFAIK)
Administrator
Moderator
News Reporter
Donator
Joined
Oct 11, 2009
Messages
3,484
Reaction score
403
Points
123
Location
Utrecht
Website
www.spaceflightnewsapi.net
I don't think so, there are other addons which have the same problem, and I don't know how to fix it. BTW, I'm using NASSP for Orbiter 2010 which it was made for so there shouldnt be any probs.

Not true. NASSP 7 is beta so there are quite a lot bugs. And about the other add-ons, this depends on the dll it uses. You can't just 'generalize' add-ons
 
Last edited:
Joined
May 8, 2011
Messages
71
Reaction score
0
Points
6
Location
Pozega, Serbia
Not true. NASSP 7 is beta so there are quite a lot bugs. And about the other add-ons, this depends on the dll it uses. You can't just 'generalize' add-ons
I don't really know, AMSO is just so much more stable than nassp, but nassp is much more realistic and animations are better, like say, at staging you can see the pressure smoke bursting out!
 

IronRain

The One and Only (AFAIK)
Administrator
Moderator
News Reporter
Donator
Joined
Oct 11, 2009
Messages
3,484
Reaction score
403
Points
123
Location
Utrecht
Website
www.spaceflightnewsapi.net
I don't really know, AMSO is just so much more stable than nassp, but nassp is much more realistic and animations are better, like say, at staging you can see the pressure smoke bursting out!

That's because AMSO is a stable release. NASSP 7 (for Orbiter 2010) is a beta.

From Their Site said:
Since Project Apollo is an open source project and all developers are working for free in their spare time we have no project plans, schedules, or things like this.

You just have to be patient for NASSP to be updated. As they said, the developers of NASSP sacrifice their free time for the development of NASSP. AMSO is from ACSoft, who are specialized in developing sim software, so they have probably more time (and experience).
 
Joined
May 8, 2011
Messages
71
Reaction score
0
Points
6
Location
Pozega, Serbia
That's because AMSO is a stable release. NASSP 7 (for Orbiter 2010) is a beta.



You just have to be patient for NASSP to be updated. As they said, the developers of NASSP sacrifice their free time for the development of NASSP. AMSO is from ACSoft, who are specialized in developing sim software, so they have probably more time (and experience).
Other than that, nassp is full of bugs, like 2D pannel lag, game crashing, wrong-positions spawning, etc.. I wonder if final NASSP version will work for me at all.
 

alagreca

Member
Joined
Jun 4, 2008
Messages
24
Reaction score
0
Points
16
Location
Texas
Website
home.myspace.com
Something you might try

Hi, I was working on this very problem about a week ago. This is what I came up with, although I cant be sure it will work on your setup. It works on mine with the latest beta and cvs updates. the hardstands do not appear properly with the external D3D9 client so use the standard orbiter.exe.

Begin code:

BEGIN_DESC
Neil Armstrong, Mike Collins and Buzz Aldrin change history forever. The first manned Lunar Landing. July 16, 1969. The scenario starts at T-2h00min and uses the quickstart realism mode. (AS-506)
END_DESC

BEGIN_ENVIRONMENT
System ProjectApollo\Sol
Date MJD 40418.4805555556
END_ENVIRONMENT

BEGIN_FOCUS
Ship Columbia
END_FOCUS

BEGIN_CAMERA
TARGET Columbia
MODE Extern
POS 14.38 0.31 -88.48
TRACKMODE TargetRelative
FOV 16.20
END_CAMERA

BEGIN_MFD Left
TYPE Map
REF Earth
BTARGET Cape Canaveral
END_MFD

BEGIN_PANEL
END_PANEL

BEGIN_SHIPS
Columbia:projectApollo\Saturn5
STATUS Landed Earth
BASE Cape Canaveral:2
POS -80.6040900 28.6083150
HEADING 270.00
FUEL 1.000
APOLLONO 11
REALISM 0
NASSPVER 70000
VECHNO 506
STAGE 5
STAGESTATUS 0
DOCKSTATE 0
SIFUELMASS 2145798.0
SIEMPTYMASS 131621.0
SIIFUELMASS 442393.0
SIIEMPTYMASS 39869.0
S4FUELMASS 107072.0
S4EMPTYMASS 12426.0
MISSNTIME -7200
TOAPO 185.94
TOPER 183.16
TOHDG 72.058
SICSHUT 135.0
SISHUT 161.63
SIICSHUT 459.8
SIIPUT 498.0
SIISHUT 548.22
IGMST 204.1
TLIMJD 40418.67850687053
LOIMJD 40421.723495
FREERETURNPECMJD 40421.723495
FREERETURNPECALT 250000
TLIOFFSETLON 0
TLIOFFSETLAT 0.106465084371654
TLIOFFSETRAD 8889734.423574794
MOONLONG 23.4333
MOONLAT 0.6875
MOONALT 0.0
MOONBASE Tranquillity-Base
MOONMJD 40422.845833
EARTHEIMJD 40426.691042
SPLASHLONG -169.1542
SPLASHLAT 13.3162
LANG English
LEMN Eagle
<Checklist>
FILE Doc\Project Apollo - NASSP\Checklists\CSM Default Checklists.xls
</Checklist>
END
Crawler-Transporter:projectApollo\Crawler
STATUS Landed Earth
POS -80.6178830 28.5957500
HEADING 69.50
LVNAME Columbia
END
ML:projectApollo\ML
STATUS Landed Earth
POS -80.6040850 28.6083990
HEADING 0.43
LVNAME Columbia
END
VAB:projectApollo\VAB
STATUS Landed Earth
POS -80.6509930 28.5860680
HEADING 77.00
LVNAME Columbia
END
MSS:projectApollo\MSS
STATUS Landed Earth
POS -80.6199090 28.5954040
HEADING 244.99
END
END_SHIPS

End code

Something I cant figure out though is how to seperate the CSM/LM from the S4B after TPD.
 
Last edited:

Tschachim

Addon Developer
Addon Developer
Donator
Beta Tester
Joined
Feb 7, 2008
Messages
300
Reaction score
0
Points
16
Location
nassp.sf.net
Website
nassp.sf.net
I've got this annoying problem with Saturn V rocket (NASSP for Orbiter 2010), when I start any scenarios with S5, It puts my rocket and its launchpad away from launch site, so It's like floating on the air. How do I fix this?

To quote myself from here: http://www.orbiter-forum.com/showthread.php?p=293889&postcount=7

Might it be that you're trying to use a scenario in the "Broken Scenarios" folder and now wonder why it's broken? ;)

To fix that, you can copy/paste the POS/HEADING settings for all vessels from the "Project Apollo - NASSP\Broken Scenarios\Virtual AGC\Apollo 8 - Launch" scenario, which should be fairly OK.

Cheers
Tschachim

---------- Post added at 11:51 AM ---------- Previous post was at 11:44 AM ----------

Something I cant figure out though is how to seperate the CSM/LM from the S4B after TPD.

Feel free to post/attach a scenario saved when you want to separate, then I'll take a look. At first glance make sure you have the pyros armed and the SECS enabled:

http://nassp.sourceforge.net/wiki/Pyrotechnics
http://nassp.sourceforge.net/wiki/Sequential_Events_Control_Subsystem

Cheers
Tschachim
 
Top