FIFE forums

Please login or register.

Login with username, password and session length
Advanced search  

News:

FIFE 0.4.0 has been released on 15th of January, 2017!

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - mvBarracuda

Pages: 1 2 [3] 4 5 ... 25
31
General discussion / Re: few questions about FIFE
« on: October 10, 2010, 10:54:20 pm »
If you're running Win32, we recommend to build via SCons as this is the easiest option for new FIFE users. You basically just need to grab the latest sources from SVN, download the FIFE win32 devkit and extract it into the right folder, run a batch file and you're done :-)

Details about the process can be found here: http://wiki.fifengine.net/Building:Win32:SCons

32
Help and troubleshooting / Re: Win XP Dependency Issues
« on: August 05, 2010, 03:22:53 am »
API docs can be found here, both for the C++ core API as well as the Python bindings:
http://fifedocs.boxbox.org

33
Help and troubleshooting / Re: i have a proplem
« on: July 06, 2010, 06:35:28 pm »
Confirmed: you need to install a 32bit Python distro to run FIFE, even on 64bit Windows systems. The only way to work around that would be to compile ALL FIFE dependencies that ship with the FIFE windows dev kit for 64bit systems. That would be a _massive_ task.

34
Help and troubleshooting / Re: error trying to build ext
« on: April 01, 2010, 07:48:05 am »
Heya Mike.

How do you try to build ext? In which folder do you invoke the build command?

Furthermore: which scons version are you running? It sounds like a problem that is caused by an outdated scons version that's not supported anymore.

36
General discussion / Cleaning up the download wiki article
« on: December 29, 2009, 03:08:35 am »
Right now the download article at the wiki is rather cluttered:
http://wiki.fifengine.net/index.php?title=Download_section

Proposals:
1. Get rid of the Fallout patches section or move it at least to a separate article.
2. Get rid of the Audio pack section or move it at least to a separate article.
3. Adjust the Linux, Mac & Win32 templates; they occupy quite some space right now and somehow look odd. Hard to properly describe it but hopefully somebody got an idea how they could be improved  (or prolly entirely removed):
http://wiki.fifengine.net/Template:Platform:Linux
http://wiki.fifengine.net/Template:Platform:Mac
http://wiki.fifengine.net/Template:Platform:Win32

37
Framework development / Re: view_performance branch testing
« on: December 29, 2009, 01:54:25 am »
Sounds great phoku :-) Keep up the good work!

38
Framework development / Re: OS X Snow Leopard - build issues
« on: December 29, 2009, 12:49:38 am »
Btw.: It looks like you can now use guichan 0.8.2 on OSX.

Quote from the IRC channel last night:
Quote
2009-12-28T23:54:43  <tommyd3mdi> Hi! Just wanted to drop in to tell you that you can remove the note about MacPorts only shipping guichan 0.8 here: http://wiki.fifengine.net/Building:Mac:SCons
2009-12-28T23:54:44  <UH-Guard2> Title: Building:Mac:SCons - FIFE development wiki (at wiki.fifengine.net)
2009-12-28T23:54:51  <tommyd3mdi> I've updated it today to 0.8.2
2009-12-29T00:01:31  <tommyd3mdi> a tiny patch is needed which is included in the MP distribution - I hope the fix will be accepted by upstream as well (see http://code.google.com/p/guichan/issues/detail?id=122)
2009-12-29T00:01:32  <UH-Guard2> Title: Issue 122 - guichan - guichan 0.8.2: linkage fails with undefined symbols under Mac OS X 10.5.8 (Intel) - Project Hosting on Google Code (at code.google.com)

39
Framework development / Re: view_performance branch testing
« on: December 09, 2009, 07:42:46 am »
Feedback from the PARPG forums:
Quote from: amo-ej1
When I run the large map on fife trunk I get 20-30 fps, with the changes in trunk I get about 200 fps (but then again we might wish to add the possibility to render the fps string inside the hud somewhere for  more easy reference. (This is in 1024x768, not fullscreen)

The only remark I have is that now I see some artifacts (apar from the PC and NPC's starting to dans at the same locatio), these artifacts are not obviously reproducible and not screenshotable :( so you may either believe me or think that i was drunk while seeing them.

What I see is the following ,when the PC is moving, i think mainly when starting or ending a movement i sometimes see black lines which oultine a horizontal/vertical/diagonal cut through the scene but still following the tile outlines. This occurs about once a minute, but i haven't found a real way to trigger this ... i don't believe I ever saw this on the trunk (not in the past, not on trunk (of parpg and fife)).

41
Framework development / Re: Building FIFE on Vista 64
« on: December 05, 2009, 10:30:52 am »
A little update from this front. One of the PARPG devs tried to build FIFE with the latest win32 devkit on his vista 64 machine. The mingw snapshot that ships with the devkit caused no trouble so you can actually now build FIFE on Vista 64 system via scons >> mingw.

That's good news as especially non-tech-savvy users are usually not keen on installing MSVC and would rather prefer to simply run a batch file to build FIFE.

42
Framework development / Re: Win32 compile SDK
« on: November 23, 2009, 08:37:23 am »
Had some more time to test FIFE with Code::Blocks today. It seems that the build issues have vanished after upgrading to the latest Code::Blocks SVN snapshot (r5911).

I've added my findings to this ticket:
http://fife.trac.cvsdude.com/engine/ticket/415#comment:3

43
Why do you have the impression that GemRB is dead? They just recently released a new version.

44
I don't see a reason why FIFE couldn't be used for such an RPG. The team I'm involved in basically works on something like that and utilizes FIFE for it:
http://www.parpg.net

Another option might be GemRB:
http://linux.prinas.si/gemrb/doku.php

Though GemRB seems to be more geared towards the Infinity Engine games. Whatever engine you'll use, it will be a long way to finish such a game. Good luck with it and keep us updated.

45
Framework development / Re: Win32 compile SDK
« on: November 16, 2009, 03:49:15 am »
Looks like support for Code::Blocks is currently broken (both for my devkit package as for cheese's ones). We should go forward with the release nevertheless but I'll create a Trac ticket for the Code::Blocks issue.

EDIT: the new Win32 DevKit has been released. Make sure you install Python 2.6! Python will not work anymore!

For details see: http://fifengine.net/2009/11/16/new-fife-win32-devkit-available/

Pages: 1 2 [3] 4 5 ... 25