Anothe rreason why I think this whole program is a fake/virus, is you claim you have 2 cores with 16 GB ram , yet your in-game Halo is running slow as hell, no audio, possible it is just a video, cause you mute it so we cant just here the main menu playing in other tabs?

well I have 4 Cores, and 10GB ram and my Halo is NO WHERE NEAR THAT LAGGY, and don't blame Camtasia, it runs much smoother on mine through camtasia, also the "yu had controls working earlier" leads more that it's fake, I could say I coded Halo 3, and I forgot, obvious lie...

If it is real, congratulations, good job, can't wait. But imho it looks a bit fake.

It could just be the recorder...

This. phantom bsp is the bane of my existence.

Camtasia Studio (The recorder he uses) is notoriously slow for recording Directx based programs. I know this because I use that as well (That's how I record my tutorials XD)


Edit: Also you guy's do know that unless he figured out a way to add something to a closed source game, all of the features you guy's are wanting for this program will never come to be.

Just making sure.
Edited by Codebrain on Jan 3, 2010 at 06:43 PM

Removing phantom BSP isn't changing the engine. Nor is any of my requests.

The engine does have a part in making "phantom bsps". It makes them because of a modeling error you might have created. The engine does it out of confusion.

Yes, but removing them doesn't effect the engine at all. Yoyorast v2 took so long to make just because of all the phantom faces. Making a quick way to remove them would be a nice addition.

Phantom faces is directly affected by the engine. Its not some random compiling error that creates a face that shouldn't be there. Its the way the collision is used in the game, a certain combination or cluster of collision geometry might result in a phantom face.

Whatever makes you happy. Removing them shouldn't be break the engine.

You read is. It the break engine, and. Yes it breaks engine.
Edited by Sprinkle on Jan 3, 2010 at 08:33 PM

Errors are there for you to fix, and to warn you for possible problems... That's what they are added for. Hell. Lets just remove all errors because we are all too lazy to fix them and have buggy maps which are unstable...

Tards...

IN game mode is working better now!

https://www.wmclan.net/e3hek/ingamemode.html

Features added...

1. Saving maps in sapien, and then building them with tool will put them in your maps folder like normal, but will immediately be available in the "in game" client. This wasn't working 100% due to needing to overwrite a map file.

2. In game mode fixed

3. No need to have sapien running if all you need is Guerilla, and vise versa. You can close, and open any apps you want at any time.

4. Added a "no error" feature to tool that will allow you to bypass errors such as bitmap power of two, etc.

5. All fields are unlocked in guerilla, without the use of Kornman's hek "which doesn't work on some systems due to dll errors!".


Things to add currently:

1. Tool crashes program if selecting more then one thing to do at the same time. Need to create a new thread for each command so you can run bitmaps, and structure at the same time etc.

I wont be impressed unless/until you make it compatible with open sauce features.

Open Sauce is next to useless.

Except that someone was kind enough to put time into adding filters and motion blur to make it visually pleasing.

Dont talk about yourself like that.

Make the "no error" mode an optional thing. I like to get my models ingame correctly and avoid any kind of errors that could cause stuff like buffered tris or those nasty black spots when you run radiosity.

.. Heh?

Why does half the community not trust E3P0 then?

Because one of his programs sent background information how the program was doing discretely without the users permission.

Basically, ^that. I've used his stuff for a while (when I had Virus Protection), like Tool Star and crap and i never found myself covered in Trojans or being hacked.

The only thing he did was in tool*
A bunch of people where hating on him because they wanted to see the errors in the maps they make. E3po fed up with it and made the tool updater delete tool* its self so no one could run it.

There was nothing in tool**, you can check the decompiled source code of previous versions that i'm sure someone has.


The only thing it did was load a web page to check for updates. That was it. How many apps do that these days?? uh... 1..2..3..4.5.6.. *looses count*


Anyway.

Some new things.. Should i try to make a new rendering engine\completely new sapien? I did manage to keep my code for reading the map information(bsp stuff). I would have to add a shader system to it.. hmm






Should i? I'm questioning if i should or not... What do you think? With time, and help, it could look great.
Edited by Fairchild on Jan 4, 2010 at 03:43 PM

I don't really see the point in doing that, the only thing sapien needs upgraded is custom resolutions instead of fixed at 640x800 or w/e

oohhhhohohh. Thank you! You just reminded me of something.. :)

(adds your name to credits list)

No one cares if you are impressed. Lol

http://img704.imageshack.us/img704/6222/hazor.png

Good job using a certain app to boost that 5.9 rating on your devmode to a 9.9 ;D.

Great work on this program I like it, release?

I don't see a reason to make a new rendering system for Sapien if it does not benefit how it looks in-game.
Custom Lightmap uvs.
Custom Lightmap uvs.
Custom Lightmap uvs.
Custom Lightmap uvs.
Custom Lightmap uvs.

This^^^

Same with item collections.

Also an updated Sapien that reloads AI as you make new encounters and stuff, like putting in Command Lists and crap you don't have to exit then reload to have everything work %100.

There is already a command that does exactly as you said.

You saying that gave me an idea....

Hot key commands for sapien, that you can assign easily. For instance.. If your working on AI, you probably would like to easily to (ai_reconnect). Go into a menu, hit your keyboard with what key you want to map to (ai_reconnect) and then boom! Anything you can do in console can be hotkeyed. Maybe even a little popup box menu with assignable buttons for commands, etc..

maybe make sapien run properly when opening a scenario. like for people with dual core processors you have to like set the affinity or whatever. that would be very helpful instead of having to set that every time or restart sapien with loading a new map, also a question does sapien update automatically if you change a tag, say you recompile a model will it update the scenery tag loaded into sapien or do you still have to reload the scenario?

nice work on this, but here is a suggestion, can you also put a map compiler in there as well, so you won't have to close that down, go into tool, compile everything, and go back in it?