Celestia Forums

I have managed to compile the latest CVS release under VS2005 and I have some questions:

1. Glutmain.cpp - is it important? (Note: I excluded it from the build)
2. Spice.lib - is there a .dll for this?
3. Joystick control - Which file has the F8 toggle in it? (Note: Its not with the rest of the key mappings)
4. 3dsmesh.cpp - This file has coding errors, is it important?
5. Lua Edu Utils - This has no effect when integrated into the extras folder and config file, am I missing some code?
6. solarsysxml.cpp - This file has coding errors, so I excluded it, is it important?
7. oggtheoracapture.cpp - Has coding errors, so it was excluded, is it important?
8. celx.cpp (celestia project) - Again, coding errors, is this important?

Some additional questions:

1. Is there any way of adding explosion effects, for example, a supernova?
2. I know that objects can be scripted, however, can I use an external app to control the movement of objects?
3. Is there any method to enable/disable rendering of specific objects, rather than entire groups?
4. How do you obtain the absolute co-ordinates of an object (i.e. planets, asteroids, satellites)?

1. Glutmain is irrelevant for Windows.

2. Updated dlls and makefiles for building with VS2005 Express are available in
http://www.celestiaproject.net/~claurel/celestia/winbuild/
This includes cspice.lib

However, it does not include updated searchlist definitions for path, library or include. I'll include below what I'm using.

3. I dunno where the F8 key command is defined.

4. There are no fatal errors when building under 32bit Windows XP using the updated script makerelease.bat. Are you using that script?
I think you're the first person to report trying to build under Vista. Are you running 32bit Vista or 64bit Vista?

I get warnings under XP in
texturefont.cpp
cmdparser.cpp
dsodb.cpp
octree.h
marker.cpp
nebula.cpp
overlay.cpp
stardb.cpp
jmorecfg.h (windef.h)
winmain.cpp
vertexlist.cpp

I get no warnings or errors compiling 3dsmesh or 3dsmodel.

Here is the script that I use for updating the path, include and library search lists. Note that you need th current Server 2003 Platform SDK, too.


5. Vincent will have to help debug your Lua Edu problems. Did you remember to modify celestia.cfg ?
Do CelX scripts work for you? If so, Lua is built into Celestia properly. If not, then you need to rebuild with Lua support.

6. the XML support is irrelevant.

7. oggtheoracapture.cpp is irrelevant for Windows.

8. celx.cpp genereates no errors for me.

----
1. Not yet.
2. Scripted orbit functions can do I/O to files.
An external app can write a file.
Some commands can be sent to the running copy of Celestia by specifying --once on the command line.
3. Not yet. But there are workarounds using Scripted Orbit functions.
4. Read the Celx/Lua documentation on Harald's web site.

1. Glutmain is irrelevant for Windows.

Sweet.

2. Updated dlls and makefiles for building with VS2005 Express are available in
http://www.celestiaproject.net/~claurel/celestia/winbuild/
This includes cspice.lib

However, it does not include updated searchlist definitions for path, library or include. I'll include below what I'm using.

Thanks, I've downloaded them and will update everything.

3. I dunno where the F8 key command is defined.

I'll try to find it.

4. There are no fatal errors when building under 32bit Windows XP using the updated script makerelease.bat. Are you using that script?
I think you're the first person to report trying to build under Vista. Are you running 32bit Vista or 64bit Vista?

No, I don't use the script. This is a pure VS2005 build from within the IDE. I provided instructions on how to setup the environment and what files to exclude in another thread. I'm using 32bit Vista, I could compile a 64bit version, but I would need the source to the libs. Using the current libs I have (winlibs-new.zip), I get 135 warnings during the build:

5. Vincent will have to help debug your Lua Edu problems. Did you remember to modify celestia.cfg ?
Do CelX scripts work for you? If so, Lua is built into Celestia properly. If not, then you need to rebuild with Lua support.

Excellent. I did modify the celestia.cfg, but I couldn't see the corresponding hooks in the latest CVS code. I just checked the CelX scripts (I used the scripts folder) and I get an error saying 'File type not recognised'.

6. the XML support is irrelevant.

One less thing to worry about

7. oggtheoracapture.cpp is irrelevant for Windows.

Excellent.

8. celx.cpp genereates no errors for me.

It generates the following errors:




----

1. Not yet.

Pity. This would be an excellent feature. A nice HDR effect would be sweet.

2. Scripted orbit functions can do I/O to files.
An external app can write a file.
Some commands can be sent to the running copy of Celestia by specifying --once on the command line.

Basically, I want to know if I can used a separate application to control the path an object takes and make course and speed corrections in real-time. Also, how would I sent these commands?

3. Not yet. But there are workarounds using Scripted Orbit functions.

I can add some fine grain controls if need be.

4. Read the Celx/Lua documentation on Harald's web site.

I'll do that.

DT wrote:

5. Vincent will have to help debug your Lua Edu problems. Did you remember to modify celestia.cfg ?
Do CelX scripts work for you? If so, Lua is built into Celestia properly. If not, then you need to rebuild with Lua support.

Excellent. I did modify the celestia.cfg, but I couldn't see the corresponding hooks in the latest CVS code. I just checked the CelX scripts (I used the scripts folder) and I get an error saying 'File type not recognised'.

I've never used the IDE, so I don't know what to suggest to ensure Lua support gets included. Looking at the makefiles may help.


----

1. Not yet.

Pity. This would be an excellent feature. A nice HDR effect would be sweet.

Maybe someday...
My understanding is that the current star database would have to be modified to take into account luminosity changes. They'd currently would require changing where a star is stored in the octree, which would be quite difficult.

2. Scripted orbit functions can do I/O to files.
An external app can write a file.
Some commands can be sent to the running copy of Celestia by specifying --once on the command line.

Basically, I want to know if I can used a separate application to control the path an object takes and make course and speed corrections in real-time. Also, how would I sent these commands?

Code to support realtime control of Celestia by an external program is not in the distributed version of Celestia. My understanding is that there have been at least two unpublished modifications to Celestia which enable tcp/ip control. A search of the Forum should locate those discussions.

A brief description of how to send commands to Celestia on its command line is in the Celestia WikiBook at http://en.wikibooks.org/wiki/Celestia/Scripting

3. Not yet. But there are workarounds using Scripted Orbit functions.

I can add some fine grain controls if need be.

I know Chris is planning to add finer grained support in a future version of Celestia, but that may not happen for a while. See the Sticky titled Celestia Development Roadmap.

I've never used the IDE, so I don't know what to suggest to ensure Lua support gets included. Looking at the makefiles may help.

I'll be able to debug this using the IDE. I'll just set a couple of breakpoints and find out what's going wrong. I think it may be to do with Celx.cpp not being present, but I don't know for sure yet.

Maybe someday...
My understanding is that the current star database would have to be modified to take into account luminosity changes. They'd currently would require changing where a star is stored in the octree, which would be quite difficult.

I can see your point. How about a different approach. I just want to add an explosion effect to the rendering pipeline. See this link for an idea:

http://http.download.nvidia.com/developer/SDK/Individual_Samples/samples.html#cg_explosion

Basically, I would like to be able to render an explosion at any co-ordinates on demand. I can create a toggle that will render, or not render, the explosion.

Code to support realtime control of Celestia by an external program is not in the distributed version of Celestia. My understanding is that there have been at least two unpublished modifications to Celestia which enable tcp/ip control. A search of the Forum should locate those discussions.

A brief description of how to send commands to Celestia on its command line is in the Celestia WikiBook at http://en.wikibooks.org/wiki/Celestia/Scripting

I check around the forum for the tcp/ip mods, thanks for that.

I know Chris is planning to add finer grained support in a future version of Celestia, but that may not happen for a while. See the Sticky titled Celestia Development Roadmap.

I think it is important. The universe changes with time and the ability to stop a single rendering an object at run-time is must for realism. For example, take the Mir space station, it would be nice to watch that burn up.

selden wrote:

DT wrote:5. Vincent will have to help debug your Lua Edu problems. Did you remember to modify celestia.cfg ?
Do CelX scripts work for you? If so, Lua is built into Celestia properly. If not, then you need to rebuild with Lua support.

Excellent. I did modify the celestia.cfg, but I couldn't see the corresponding hooks in the latest CVS code. I just checked the CelX scripts (I used the scripts folder) and I get an error saying 'File type not recognised'.

Hi,
Have you correctly placed the 'luahookinit.lua' file in your Celestia base folder ?

1- Unzip and paste the lua_edu_tools' folder in the 'extras' folder.
2- Paste the 'luahookinit.lua' file directly in your Celestia base folder.
3- Add the following line to your celestia.cfg file :

Code: Select all

Configuration
{
LuaHook "luahookinit.lua" # <-- Line to add
...

Have you correctly placed the 'luahookinit.lua' file in your Celestia base folder ?

Yes I have Vincent. I made sure to double checked everything before I posted. I spent 2 days reading the forums before I joined.

The issue appears to with Celx.h/Celx.cpp in the Project Celestia. I dropped them from the build and I got it compile.

Selden give me a link for the latest libs and I added them to the project. Using the latest Lua libs, I get 16 errors when compiling the project with the celx files included:




If I revert to the older Lua headers (all dated 2004), I get on 9 errors when I compile with the celx files included:




If I exclude celx.h and celx.cpp from the build all the errors vanish. The solution builds and I get a functional copy of Celetia 1.5.0.

The only problems are the following:

1. Loading scripts fails with a message box saying 'invalid filetype'.
2. Lua Edu Tools does not function whatsoever.

Ok, I checked out Compiler Error C2248:

Error Message
'member' : cannot access 'access' member declared in class 'class'


Members of a derived class cannot access private members of a base class. You cannot access private or protected members of class instances.

See Knowledge Base article KB243351 for more information on C2248.

http://msdn2.microsoft.com/en-us/library/tsbce2bh(VS.80).aspx

So a quick hack was to make the private members, of celestiacore.h, public.

Not pretty, but it works. I rebuilt and I am now down to two errors:

Scratch that:

I had forgotten to define CELX and increase the LUA_VER to 0x050100.

Just rebuilt and tested it. I've got the overlays working and scripts are fully functional.

I must add this to the primer...

DT wrote:Scratch that:

I had forgotten to define CELX and increase the LUA_VER to 0x050100.

Just rebuilt and tested it. I've got the overlays working and scripts are fully functional.

Good ! Let me know if you have any problem with the Lua Tools.

Good ! Let me know if you have any problem with the Lua Tools.

I've had a good test run and they seem to working fine. I prefer the on-screen menu system.

What would be nice is the following:

1. Replace all Menu bar functions with the overlays.
2. Create a way to toggle which options you would like displayed and where.
3. Remove the Menu bar completely

I'm sure that's were your heading and its looking really good so far.

DT wrote:

Code: Select all

Error   91   error C2039: 'configParams' : is not a member of 'CelestiaConfig'   d:\cvs\celestia\src\celestia\celx.cpp   5899
Error   92   error C2227: left of '->getString' must point to class/struct/union/generic type   d:\cvs\celestia\src\celestia\celx.cpp   5899

I have got these two errors but I don't know how to resolve it, how do you do ?

Thx for the help.

I have got these two errors but I don't know how to resolve it, how do you do ?

Refer to the Update I added to the bottom of the Primer:

UPDATE: 28th Aug 2007

Add celx.h and celx.cpp to the Project celestia...

Obtain the latest libs:

http://www.shatters.net/~claurel/celestia/winbuild/

...add the following libs to the celestia Project:

lua5.1.lib, lualib.lib, ijgjpeg.lib, lua.lib

Define CELX and increase the LUA_VER to 0x050100 (celx.h)

http://shatters.net/forum/viewtopic.php?t=11419&start=0&postdays=0&postorder=asc&highlight=

DT wrote:2. Create a way to toggle which options you would like displayed and where.

This is already possible by editing the config.lua file.
The last version of the Lua Tools is available here:
http://celestiaproject.net/forum/viewtopic.php?t=10352

Is this the one you've tested ?

PS: We may continue this discussion in the relevant topic:
http://celestiaproject.net/forum/viewtopic.php?t=10352

I've come across a rather weird problem. Textures are not being mapped onto the planets. Textures are being mapped onto earth, but not the rest.

Any ideas?

Don't know where to post that: CVS seems broken under Linux today. Removing 'Celestia.dsw' from src/Makefile.am seems to solve.

Mathieu

mjoubert wrote:

Code: Select all

make[3]: *** No rule to make target `Celestia.dsw', needed by `all-am'.  Stop.

Don't know where to post that: CVS seems broken under Linux today. Removing 'Celestia.dsw' from src/Makefile.am seems to solve.

Celestia.dsw was removed from CVS because it's completely out of date. It's an MS Visual Studio file, so I didn't expect it would affect the Linux build. I'll remove it from src/Makefile.am on CVS.

--Chris

Now Celestia-KDE is even more upset

./celengine/celestia.h:13:5: warning: "_MSC_VER" is not defined

...

make[3]: *** No rule to make target `Celestia.dsw', needed by `all-am'. Stop.


Bye Fridger

t00fri wrote:Now Celestia-KDE is even more upset

./celengine/celestia.h:13:5: warning: "_MSC_VER" is not defined

...

make[3]: *** No rule to make target `Celestia.dsw', needed by `all-am'. Stop.


Bye Fridger

Oops. I messed up the nesting of the #define. Oddly enough, it worked when I built with MinGW, which shouldn't defined _MSC_VER.

--Chris

Fine now with _MSC_VER

But Celestia-KDE still dies with

make[3]: *** No rule to make target `Celestia.dsw', needed by `all-am'. Stop.

Celestia-gtk and Celestia-gnome compile fine under my new OpenSuse 10.3 installation.


Bye Fridger