Trying again :)

  • Thread starter Thread starter Sebanisu
  • Start date Start date
Status
Not open for further replies.
i have mostly fixed the package building and have to update a few files.

currently im unable to start q-gears as i get an error then it dies

[ERROR] /home/chris/q-gears_0.21/QGearsMain/src/core/DebugDraw.cpp 58: Could not find font "CourierNew" for debug draw.
Click to expand...
aparently i don't have CourierNew font (i do have it althought on my system its Courier New)

reading up on this seams we need a fontdef for all fonts ? . since the files and the font will need including in the project perhaps a free font is good for this (freemono,free sans come to mind) . Any suggestions let me know ill try them.
 
I'm kinda scratching my head to why I'm getting this glitch
1icsw1.png


the screen is being drawn in the top left corner. I think I'll try disabling my dual monitor setup and see if that fixes it.

But I'm pretty sure when I just built with cmake and mingw it didn't do this.

sithlord:

Any free font should do for that debug text. I'm unsure how font's are handled I spent a few mins skimming over the documentation.
You could add another few lines of code after the thing and maybe make it try another font. I'm not entirely sure how fonts are handled though I only skimmed over the documentation

before:
Code: [Select]
Code: 
    m_Font = Ogre::FontManager::getSingleton().getByName( "CourierNew" );    if( m_Font.isNull() )    {        LOG_ERROR( "Could not find font \"CourierNew\" for debug draw." );    }
after:
Code: [Select]
Code: 
    m_Font = Ogre::FontManager::getSingleton().getByName( "CourierNew" );    if( m_Font.isNull() )    {//        LOG_ERROR( "Could not find font \"CourierNew\" for debug draw." );          m_Font = Ogre::FontManager::getSingleton().getByName( "thisotherfont" );          if( m_Font.isNull() ) {                 LOG_ERROR( "Could not find font \"CourierNew\" or this other font for debug draw." );          }    }
 
accually it seams tha the data location in the resouces.cfg is messed up ..
something changes when using the --resources-file switch


Edit: completely wrong about switches not working...
 
Last edited:
--deleted--- misunderstood so I said something that was wrong.
 
Last edited:
the whole point of the switches is so that i can set resource path for linux (/usr/share/q-gears/data) is the data folder /usr/share/q-gears/ contains the .cfg files. im going to try with out the switches. once those are working the package will install a working copy (always a plus lol)
 
I tweaked the code to run qgears in a window.

Now i can run in multi monitor. I'm not sure why it wasn't workin.
 
hmm Now that I got something working that I can fiddle with. I wonder what goal I should have. What thing I should try to work on?

Should I start a new thread and let this thread end?
 
qgears should run in windowed mode all by it self, not sure maybe I changed it to respect the ogre config window, you could try to reverse your changes delete the ogre.cfg (maybe qgears.cfg) to get the config window again and just disable fullscreen in the ogre config dialog

as for what todo
only thing that comes to my mind would be to try and run qgears on some of the original ff7 files, check out the unit tests maybe, I left the resource paths etc in the code and I'll try to be available on irc, I'm on gmt+2 though
maybe we should try and get a ticketing system :D
source forge most likely has one the project owner would just need to enable it :)

the command line switches should actually work, I use the program-options package from boost for that, so maybe just the right version is needed, maybe you could come up with a unit-test for them?
 
Which irc server and channel you guys use?

I'm not sure what to do for unit tests. Since I haven't wrote any of this, I'm not sure how it all works. I spent some of last night trying to follow along. Maybe I should run in debug mode and step. hmm
 
I meant merely running the unit tests there is a build target for the tests if u enabled them in the cmake config and there is an executable for every test after building to run them separately
 
Status
Not open for further replies.
Back
Top