Chawaka
-
Posts
18 -
Joined
-
Last visited
-
Days Won
1 -
Feedback
0%
Content Type
Forums
Store
Third Party - Providers Directory
Feature Plan
Release Notes
Docs
Events
Posts posted by Chawaka
-
-
I went to compile the mainline source on FreeBSD 9.2 64bit and that's what I got.. Does anyone by a slim chance know a fix for this?
compile BattleArena.cpp compile FSM.cpp compile MarkConvert.cpp compile MarkImage.cpp In file included from debug_allocator.h:5, from stdafx.h:7, from MarkConvert.cpp:1: /usr/include/c++/4.2/new:95: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:96: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:99: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:100: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:105: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:106: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter compile MarkManager.cpp In file included from BattleArena.cpp:6: char.h:729: error: integer constant is too large for 'long' type In file included from debug_allocator.h:5, from stdafx.h:7, from BattleArena.cpp:1: /usr/include/c++/4.2/new:95: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:96: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:99: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:100: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:105: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:106: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter In file included from debug_allocator.h:5, from stdafx.h:7, from MarkImage.cpp:1: /usr/include/c++/4.2/new:95: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:96: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:99: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:100: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:105: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:106: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter gmake: *** [OBJDIR/MarkConvert.o] Error 1 gmake: *** Waiting for unfinished jobs.... gmake: *** [OBJDIR/MarkImage.o] Error 1 In file included from debug_allocator.h:5, from stdafx.h:7, from MarkManager.cpp:1: /usr/include/c++/4.2/new:95: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:96: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:99: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:100: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:105: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:106: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter gmake: *** [OBJDIR/BattleArena.o] Error 1 gmake: *** [OBJDIR/MarkManager.o] Error 1
-
Humm the db structure from Shogun has problems it'll bring you connection refused, fdwatch and apples and oranges..
-
Designer That's me. All of it.
-
chmod 777 your auth, game and db cores.
i doubt that the files are actually in the called path from the sh script.
you could also be missing on the shortcuts.
- 1
-
you'd try to direct the lower effect more towards him, so it'd really wrap around his body. Same goes with the fire effect, it'd be more closer to his shoulders. Play a bit with it, that creates a better flow.
But really, the idea is good and it really looks pretty, but you shouldn't overload the picture with too much effects. The eyecatcher should be the ninja with his effects, not the effects by themselves. It's not meant in a bad way, you really did a good job there
That's been helpful to me shedding some light on the flaws, thank you man. I agree with you about the effects, they indeed feel overloaded on the render and are pretty much taking over it. The surrounding flame ring was also kind of a mess and lacking that kind of realisticness in effect, so I adjusted all that in this new Sexy version with one more render being finished as well!
- 1
-
Include the effect in the NPC's msm.
- 2
-
Heyhey!
So I just finished manipulating this bad boy render and I wanted to hear your opinions about it
- 9
-
UPDATE
retouched it a little bit!
click on image for high resolution.
edit: i made this just for fun in my spare time. in case your gon be using it i dont need the rank thingy you just have fun with it
- 3
-
!@#$%^&
-
I don't think such tools are ever helpful for beginners cause they are rather unlikely to learn anything from using eased tools and stuff..
mainline compiling problems
in Community Support - Questions & Answers
Posted
I think the problem is that I'm on 64 bit.. Gonna try 32bit and see if that works out...