Crystal Space
Welcome, Guest. Please login or register.
October 22, 2014, 01:37:06 am

Login with username, password and session length
Search:     Advanced search
9010 Posts in 2044 Topics by 8780 Members
Latest Member: Robertt56
* Home Help Search Login Register
  Show Posts
Pages: [1] 2
1  Crystal Space Development / Support / Re: Jamming problems with cal3d on: October 15, 2006, 07:56:21 pm
Stupid computer!! *angry*

Here's the patch. And you have to remove the .txt from the end. This forum doesn't let you post .cpp files.
2  Crystal Space Development / Support / Re: Jamming problems with cal3d on: October 15, 2006, 07:54:07 pm
Had this exact same error. Here is the post: http://community.crystalspace3d.org/forum/index.php/topic,1299.0.html

Basically, there is a bug in crystal space code, and a file needs a patch. My post links to that patch.

Or, you can just download the file I'm posting, and place it in $CRYSTAL/plugins/mesh/sprcal3d/object/

A purist might say that this isn't a bug in crystal space, but rather the implementation of cal3d changed. However, I say that since the instructions are to download the latest cal3d, rather than a specifc cal3d, the fact that crystal space aims at a moving target and misses, crystal space still misses it's target. If they didn't want to aim at a moving target, they should have specified which version to download, or offer a working version on this site.

Anyway, replace this file, and it should work. Oh yeah, and it works with cal3d revision 420 (I think 425 too). If you use a newer version, I doubt you'll have any problems, but no gaurantees from me. It is, after all, a moving target.
3  Crystal Space Development / General Crystal Space Discussion / Re: Development state of 1.0 on: October 15, 2006, 07:42:52 pm
Soo..., is that a "yes"?
4  Crystal Space Development / General Crystal Space Discussion / Re: Development state of 1.0 on: October 15, 2006, 02:36:21 am
So, /trunk is the newest, and those changes get ported over to /branches/release/v1.0? Does that mean that /branches/release/v1.0 will usually be stable and compilable? Sometimes it helps to spell these things out. And please correct me if I'm wrong.
5  Associate Projects / CEL Discussion / Conclusion on: October 14, 2006, 03:40:41 am
This concludes this thread.

I am almost positive that installing a recent revision of cal3d is required for celtst to run. pseudo-stable crystal will not install with latest cal3d, or revision 425 of cal3d. However, if you apply a patch to crystal, which can be found on this page:
http://www.mail-archive.com/crystal-main@lists.sourceforge.net/msg01071.html
then you can install it.

Whew! That is a lot of work to get the test apps to run! This really should be in the docs.
6  Associate Projects / CEL Discussion / Re: celtst fails to run. on: October 14, 2006, 03:25:41 am
Lots more to report:

1) Downloaded and insatlled cal3d. The latest revision is not compilable due to configuration bugs. Revision 425 is compilable though. It is only three weeks old, and is plenty "sufficient" enough for psuedo stable crystal.

2) When jamming crystal, I get errors installing cal3d. Here is an excerpt:
Code:
C++ ./out/linuxx86/optimize/plugins/mesh/sprcal3d/object/sprcal3d.o
plugins/mesh/sprcal3d/object/sprcal3d.cpp: In member function `virtual void cspluginSprCal3d::csSpriteCal3DMeshObjectFactory::HardTransform(const csReversibleTransform&)':
plugins/mesh/sprcal3d/object/sprcal3d.cpp:658: error: 'class CalCoreSkeleton' has no member named 'getListRootCoreBoneId'
plugins/mesh/sprcal3d/object/sprcal3d.cpp:659: error: 'class CalCoreSkeleton' has no member named 'getListRootCoreBoneId'
plugins/mesh/sprcal3d/object/sprcal3d.cpp:679: error: `CalTransform' undeclared (first use this function)
plugins/mesh/sprcal3d/object/sprcal3d.cpp:679: error: (Each undeclared identifier is reported only once for each function it appears in.)
plugins/mesh/sprcal3d/object/sprcal3d.cpp:679: error: template argument 1 is invalid
plugins/mesh/sprcal3d/object/sprcal3d.cpp:679: error: template argument 2 is invalid
plugins/mesh/sprcal3d/object/sprcal3d.cpp:679: error: invalid type in declaration before '=' token
plugins/mesh/sprcal3d/object/sprcal3d.cpp:679: error: 'class CalCoreAnimation' has no member named 'getPoses'
plugins/mesh/sprcal3d/object/sprcal3d.cpp:680: error: request for member `size' in `poses', which is of non-class type `int'
plugins/mesh/sprcal3d/object/sprcal3d.cpp:684: error: 'class CalCoreSkeleton' has no member named 'getListRootCoreBoneId'
plugins/mesh/sprcal3d/object/sprcal3d.cpp:685: error: 'class CalCoreSkeleton' has no member named 'getListRootCoreBoneId'
plugins/mesh/sprcal3d/object/sprcal3d.cpp:688: error: 'class CalCoreAnimation' has no member named 'getTrackAssignment'
plugins/mesh/sprcal3d/object/sprcal3d.cpp:692: error: `tf' undeclared (first use this function)
plugins/mesh/sprcal3d/object/sprcal3d.cpp:692: error: invalid types `int[unsigned int]' for array subscript
plugins/mesh/sprcal3d/object/sprcal3d.cpp:702: error: 'class CalCoreAnimation' has no member named 'setPoses'

    g++ -c -o ./out/linuxx86/optimize/plugins/mesh/sprcal3d/object/sprcal3d.o -I. -I./include -I./include -Wall -Wno-unknown-pragmas -pipe -march=i586 -I/usr/local/include -fno-exceptions -O3 -fomit-frame-pointer -ffast-math -fPIC -I/opt/
l3d-svn-r425/include  plugins/mesh/sprcal3d/object/sprcal3d.cpp

...failed C++ ./out/linuxx86/optimize/plugins/mesh/sprcal3d/object/sprcal3d.o ...
...skipped sprcal3d.so for lack of <plugins!mesh!sprcal3d!object!>sprcal3d.o...

getListRootCoreBoneId is not a valid function mentioned in any of cal3d header files. There is a similarly spelled line in cal3d_wrapper.h, but it is commented out:
//  CAL3D_WRAPPER_API std::list<int>& CalCoreSkeleton_GetListRootCoreBoneId(struct CalCoreSkeleton *self);
That is one line.

That is as far as I am so far with crystal bugs. Can anyone confirm or disaffirm whether or not installing cal3d is required in order to run celtst in C.E.L? Thank you.
7  Associate Projects / CEL Discussion / celtst fails to run. on: October 13, 2006, 11:27:51 pm
Debian Sarge
Crystal/Cel version: psuedo-stable
gcc 3.4
PNY Verto GeForce FX 5500 AGP 8x
Latest Debian stable nvidia driver

I already compiled CS and sort of got it to start working. I then compiled CEL. I made sure the environment variables CRYSTAL and CEL were set properly. I then tried to run celtst. I got the following:

wk@ALPHA:~/cel$ ./celtst
DEBUG: Sound System: Software Renderer Initializing..
DEBUG: Sound System: Configured for driver [crystalspace.sndsys.software.driver.oss]
Sound System: OSS driver for software sound renderer initialized.

crystalspace.pluginmgr.loadplugin:
  could not load plugin 'crystalspace.mesh.loader.factory.sprite.cal3d'
crystalspace.maploader.parse.meshfact:  Error loading plugin 'crystalspace.mesh.loader.factory.sprite.cal3d'!
[node: library,meshfact(name=test),plugin]
cel.pfmesh.loadmeshfactory:  Error loading mesh object factory or library 'cally.cal3d'!

crystalspace.maploader.parse.region:
  <renderpriorities> is no longer supported!
[node: world]
Load TYPE plugin crystalspace.mesh.object.haze
Print: Hello world!
Print: Hello world (small)!
Segmentation fault
wk@ALPHA:~/cel$

I looked in the data directory and found cally.cal3d and a cally directory. vfs.cfg seems to be set correctly. Why won't the test application run after a basic compile? I didn't "install" cel. CEL is set to "home/wk/cel" But I did try to install. It didn't work either.

I looked on this forum, and it seems a cal3d library has to be installed? I found no mention of that in the docs. Where do I download it? How do I install it? Or does that not apply here?

Also, I tried to compile the source code in apps/celtest/, and my application got further. Here is the errors from when I compile it manually:

wk@ALPHA:~/cel/apps/celtest$ ./celtest -relight
DEBUG: Sound System: Software Renderer Initializing..
DEBUG: Sound System: Configured for driver [crystalspace.sndsys.software.driver.oss]
Sound System: OSS driver for software sound renderer initialized.
cel.persistence:  Error opening file 'basic_level.xml'!
celtest:  Error loading level 'basic_level.xml' at '/cellib/lev'!
wk@ALPHA:~/cel/apps/celtest$

basic_level.xml is there. So are basic_entities and basic_world.

What could be wrong?
Thank you.

UPDATE: When I copy $CEL/vfs.cfg and $CEL/data/*(recursive) into $CEL/apps/celtest, then when I compile celtest myself I get the same errors I do when I try to run $CEL/celtst.

Also, I discoverd cal3d. It is an external library not mentioned as required in the CEL docs. I installed it. But it doesn't help. Also, I noticed that cal3d is included in the CS plugin directory, but not the CEL plugin directory. I still can't get this to work.

Thank you for any help.
8  Associate Projects / CEL Discussion / Re: finally got something compiled on: October 13, 2006, 10:55:58 pm
It's comforting to know that I'm not the only having problems compiling basic stuff. I look thru the forums when I'm having problems that are difficult for me to solve, and the problems are almost always more advanced than mine. I haven't found an example of another person having one of my problems. So, thanks for the spirit boost.
9  Crystal Space Development / General Crystal Space Discussion / Re: Age Limit? on: October 13, 2006, 04:17:07 pm
There is no age limit or requirement for using any free software. Nor for any proprietary software I can think of.

However, a lot of things are easier when you're 18. You need to be 18 for a credit card. Credit cards make it easier to buy stuff online, like web hosting. If you want to charge for your game, you might need a merchant credit card account, which you also have to be 18 for. A lot of banks will give debit cards to people who are 15-16. They probably can't be used as credit cards, but a lot of internet sites accept debit cards. Most adults, such as loan officers, venture capitalists, and job interviewers, will take you more seriously the older you are, to a point. They're funny that way.

You can buy debit cards that double as credit cards from most grocery stores with cash. You have to pay extra though. Fees. Or you can ask your parents, which, of course, is never as easy or convenient as doing it yourself though.

But really, to make a game, it doesn't matter how old you are. And any obstacles, like paying for web hosting, you can get around if you really want to.
10  Crystal Space Development / General Crystal Space Discussion / Re: Tips for newbies like me. My experiences with crystal space. on: October 13, 2006, 04:04:34 pm
We are not aware of problems with gcc-3.3. Can you tell me what goes wrong?

Remember all those problems I was having getting walktest to run with the latest svn crystalspace? Where I would jam it, then couldn't get walktest to run. Well, I compiled again this morning with gcc-3.4. It works much, much better. I can run walktest. It's a castle! I get errors about objects not being closed, an occasional X error, but it runs. I have to admit that I also updated svn this morning, and several files had been updated, but I do that everytime. The only thing I did differently, when it started working, was using gcc-3.4 instead of 3.3.

Could be a coincidence, since I did update svn, but I'm leaning towards not.
11  Crystal Space Development / Support / Re: Can't compile simple.cpp with event handling. on: October 13, 2006, 01:25:43 pm
Checked out svn again a few hours ago. And I compiled using gcc-3.4 (latest debian sarge version, 3.4.3), rather than gcc-3.3. I noticed in the manual that it suggests 3.4 or above, but it does not say that 3.3 is unsupported.

3.4 makes a world of differnce. Yeah, there are still errors, glitches, and bumps. But, if you compile svn with 3.4, walktest will run. It's a castle. In spite of the fact that the castle appears to be simpler, it is much, much slower than the map that walktest uses by default in pseudo stable. It might be the errors. I have them here:

wk@ALPHA:/mnt/hdb2/svn/crystal$ ./walktest -relight -fs
DEBUG: Sound System Software Renderer Initializing...
WARNING! Object 'Cube.582' is not closed!
WARNING! Object 'Cylinder.232' is not closed!
WARNING! Object 'Cylinder.230' is not closed!
WARNING! Object 'Cylinder.012' is not closed!
WARNING! Object 'Cube.580' is not closed!
WARNING! Object 'Cube.578' is not closed!
...
Total level load time: 5.682 seconds
Cleaning up...
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  4 (X_DestroyWindow)
  Resource id in failed request:  0x1200003
  Serial number of failed request:  133
  Current serial number in output stream:  135
wk@ALPHA:/mnt/hdb2/svn/crystal$

I'm still new to crystal space, so I don't know if those are serious or not. Anyway, that is latest svn walktest running from installation directory, where program is "jammed" in the source tree. Actually installing crystal space will always break it, at least with every test I've done.

Jorrit, I've asked you before what version of gcc you use, and you didn't respond. I can respect your reasons, whatever they might be. Are there any developers willing to share what environment they develop and test crystal space on/for? That would be really helpful for those of us using different environments. Thank you.
12  Crystal Space Development / General Crystal Space Discussion / Tips for newbies like me. My experiences with crystal space. on: October 13, 2006, 01:22:19 pm
I have compiled different versions of crystal space about a dozen times in the past few days. Here are a few things I've noticed.

1) compiling with gcc-3.3 does not appear to be supported, or tested at all. The instructions recommend 3.4 or higher, but no mention is made of any unsupported gcc versions. I recommend against this version, and using a newer one if possible.

2) Actually installing crystal space breaks it every time. This is only what I personally have noticed, mind you. Other people may have gotten it to install to directories, but I haven't. I've heard from a/the site administrator that installing often breaks crystal space. Unfortunately, I could not find any information about this in the docs.

By installing, I am referring to the "make install" step. Don't do that. cd into the directory you compiled crystal space, and export CRYSTAL=`pwd`. Contine using this as crystal space's root. Do not make clean.

3) Use a Makefile, don't use gcc on the command line. I had issues with this, which turned out to not be the fault of crysal space, but the fault of my own ignorance. Still, due to the complexities of any project involving crystal space, I would recommend using a Makefile, or resorting to it if you have any difficulties, especially linking related.

The default crystal space programs, like walktest, simple1, and simple2, often segfault. They often have unexplainable errors. I've compiled several times, using pseudo-stable and latest svns over a few days, using gcc-3.3 and 3.4, and sometimes they run, sometimes they don't. Sometimes they run with errors, sometimes they run clean. That's just how it is.

Remember, no matter what version of crystal space you use, it is beta. There is no stable version, even the stable version. From what I've seen, it is a very nice program. But if you can't stand hiccups, it might not be right for you.
13  Crystal Space Development / Support / Re: Can't compile simple.cpp with event handling. on: October 13, 2006, 07:43:29 am
With your help, Jorrit, I solved the original problem, that of not being able to get simple.cpp with event handling to compile. The problem was, that when coming up with the link line, I only added `cs-config --libs` to the link line I already had. I didn't think that adding extra library lines to the link line would hurt, but apparently it does. I think it is because, like you said, the linker is one pass. Note that I only got pseudo-stable crystal to work. SVN crystal still causes simple programs to segfault. (SVN as of this morning PST). I'll be checking out SVN again in a week or two.

Speaking of SVN, did the gdb info I sent help?

EDIT: When I wrote this, I didn't see your previous message. 2 pages...
14  Crystal Space Development / Support / Re: Can't compile simple.cpp with event handling. on: October 12, 2006, 03:22:44 pm
Okay, did that. Or, what I could

gdb ./walktest
gdb > run

It doesn't crash. Rather, I get a hollow window, which will not close. It won't kill either, without the -9 option. However, running ./walktest from the command line, not inside of gdb, it does crash as it did before.

So, I altered your instructions a bit. I don't know if this will give you the info you need. Here is what I followed:

./configure --enable-debug
./jam
(wait 30-45 min)
gdb ./walktest
gdb > run
kill -9 <walktest pid> (from different workspace)
gdb > where

Here is the output:

wk@ALPHA:~/svn/crystal$ gdb ./walktest
GNU gdb 6.3-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-linux"...Using host libthread_db library "/lib/tls/libthread_db.so.1".

(gdb) run
Starting program: /home/wk/svn/crystal/walktest
[Thread debugging using libthread_db enabled]
[New Thread 1076316960 (LWP 10999)]
DEBUG: Sound System Software Renderer Initializing...  (This is where I killed it)
[New Thread 1128934320 (LWP 11002)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1076316960 (LWP 10999)]
0x42bfb188 in scfImplementationPooled<scfImplementation1<CS::Plugin::XMLShader::csReplacerDocumentNodeIterator, iDocumentNodeIterator> >::operator new ()
   from /home/wk/svn/crystal/xmlshader.so
(gdb) where
#0  0x42bfb188 in scfImplementationPooled<scfImplementation1<CS::Plugin::XMLShader::csReplacerDocumentNodeIterator, iDocumentNodeIterator> >::operator new ()
   from /home/wk/svn/crystal/xmlshader.so
Error accessing memory address 0x42bfb160: No such process.
(gdb)

Does that help?
15  Crystal Space Development / Support / Re: Can't compile simple.cpp with event handling. on: October 12, 2006, 02:03:53 pm
All righty. Here it is, in the attachment. It is kind of long. But you were probably expecting that.
Pages: [1] 2
Powered by MySQL Powered by PHP Powered by SMF 1.1.2 | SMF © 2006-2007, Simple Machines LLC Valid XHTML 1.0! Valid CSS!
Page created in 9.2 seconds with 16 queries.