Meadville Space Center
Welcome, Guest. Please login or register.
September 23, 2020, 11:05:01 PM

Login with username, password and session length
Search:     Advanced search
Project Apollo - NASSP 6.4.3 released!
http://nassp.sf.net
25068 Posts in 2094 Topics by 2266 Members
Latest Member: twa517
* Home Help Search Login Register
+  Meadville Space Center
|-+  Project Apollo - NASSP
| |-+  Project Apollo - NASSP News & Discussion
| | |-+  Support & Bugs (Moderators: movieman, Tschachim, Swatch, lassombra)
| | | |-+  Testing collision detection
« previous next »
Pages: [1] Print
Author Topic: Testing collision detection  (Read 1513 times)
FordPrefect
Project Team Member
Sr. Member
****
Posts: 268



View Profile Email
« on: June 14, 2009, 12:10:34 PM »

I wanted to test Artlav's latest collision module with NASSP, though my Orbiter crashes after initialization:

Quote
Finished initialising world
>>> ERROR: Missing texture: ProjectApollo/AST_TEXT.dds
>>>        [C:\Source\Orbiter\Texture.cpp / 781]

I am using the modules released 2009-03-22. Would I need modules compiled with the latest sources to solve this problem? Compiling is still somewhat way above my head. If AST_TEXT is a texture within a module a simple CVS update wouldn't cure the problem.
Logged

My Project Apollo work in progress:
* New detailed Lunar Module Ascent stage with virtual cockpit (VC currently planned as eye candy only) 18 % done

My Project Apollo work to be continued:
* new Service Module SPS engine bell
* various Saturn V textures, exhaust textures
* SIM Bay for the SM


My long-term plans are to create a:
* New detailed Lunar Module descent stage (eventually models of all flown LM's)
* New F-1 engines for the S-1C stage showing the foil (batting) insulation
* New LUT and launch pad (if nobody else does it)
Artlav
Full Member
***
Posts: 36


746021
View Profile WWW
« Reply #1 on: June 14, 2009, 12:31:10 PM »

If by latest you mean 090613, then it's perfectly normal, since the interface was changed.
In that case, here is the compiled current state, that should work fine:
http://orbides.1gb.ru/orbf/projectapollo_modules_090614_wtw.zip (29Mb)

The texture error in the log appears wholly unrelated to the crash.

Also, question to developers:
Why pack panels and other bitmaps into dll's?
It makes for a lot of download of a lot of dead weight on the bad side, with nothing obvious on good side.
Logged
FordPrefect
Project Team Member
Sr. Member
****
Posts: 268



View Profile Email
« Reply #2 on: June 14, 2009, 01:58:59 PM »

Thanks Artlav for you speedy reply and the newly compiled modules!  Thumbs Up The crash no longer occurs, so I am testing it now...
Logged

My Project Apollo work in progress:
* New detailed Lunar Module Ascent stage with virtual cockpit (VC currently planned as eye candy only) 18 % done

My Project Apollo work to be continued:
* new Service Module SPS engine bell
* various Saturn V textures, exhaust textures
* SIM Bay for the SM


My long-term plans are to create a:
* New detailed Lunar Module descent stage (eventually models of all flown LM's)
* New F-1 engines for the S-1C stage showing the foil (batting) insulation
* New LUT and launch pad (if nobody else does it)
Tschachim
Project Apollo - NASSP
Administrator
Hero Member
****
Posts: 3700


nassp.sf.net


View Profile WWW
« Reply #3 on: June 18, 2009, 10:45:57 AM »

Also, question to developers: Why pack panels and other bitmaps into dll's? It makes for a lot of download of a lot of dead weight on the bad side, with nothing obvious on good side.

I forgot to answer that: No technical reason, it was already this way when I joined the team a couple of years ago, probably because the Deltaglider does it this way. Are bitmaps as resources within dll's bigger then separate files?

Cheers
Tschachim
Logged

Artlav
Full Member
***
Posts: 36


746021
View Profile WWW
« Reply #4 on: June 18, 2009, 10:54:58 AM »

I forgot to answer that: No technical reason, it was already this way when I joined the team a couple of years ago, probably because the Deltaglider does it this way. Are bitmaps as resources within dll's bigger then separate files?
Not quite, it's just that you need to download same 30Mb of bitmaps every time someone rebuilds the modules for you.
Same weird case is why the sources are in the orbitersdk\samples directory?
Makes more sense to put them into a special folder.

Both are nothing critical, just some WTF kind of structures in the project.
« Last Edit: June 18, 2009, 10:56:55 AM by Artlav » Logged
Swatch
Moderator
Hero Member
****
Posts: 1003


jasonims
View Profile
« Reply #5 on: July 04, 2009, 01:21:20 PM »

I have often wondered this too (the bmp in dll), but my only question would be if there is a performance benefit from where we have them?  I do know that one advantage come release time is that all the people will need are the modules themselves, not the source files, and theoretically it is a form of protection on the files (but our liscense doesn't really care or abide by that thinking).
Logged

My Project Apollo Work:
CM Visual
 -VC (~75% complete: texture work beginning again; mesh-78%; texture-70%)
Propulsion Particle Improvements (Focused on S1B right now, BETA 1.0 has been commited)
New Docking Method (~50% complete: research complete; coding partially completed, testing not underway)

Future Work:  (if it's here, it's deemed unnecessary to upcoming release)

Older Work:  (if it's here, it's fair game to whoever wants to improve)
EMS Implementation (committed: minor flaws, but groundwork is there, needs extensive testing)
EMS scrolls (committed: not refined, but usable)
SM Visual (committed: mesh-finished, texture-60%; possibly revisited in future)
J2 Texture (commited: room for improvement)
LRV (committed: mesh-finished, texture-90%; in future a ground up rebuild may be in order, but not on my plans)
Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.10 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!