Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

FPSC Classic Product Chat / 1.17 turning shaders off, and darkAI allys not shooting issues

Author
Message
raymondlee306
16
Years of Service
User Offline
Joined: 24th Oct 2009
Location: Ohio
Posted: 9th Sep 2010 03:49
Hey all,

I have 2 problems going on. The first is that even though I turn postprocessing and newblossershaders to zero (while fps creator is not running) in both the buildsetup and setup files in the fps creator folder, when I build a game they both magically turn back to 1 and also turn them on in my build file. I had to sacrifice on the video card in my new laptop to get the ram, processor, etc I wanted and can't run games with these on. This only started 2 days ago. Before that they would stay off. I tried rerunning the 1.17 update install and fps cleaner but no effect.

The second problem is with dark AI. I give the ally's appear script the "appear-ally-team1" the enemies the "appear-enemy-team2" and both the "main-weapon" script in the main slot. The enemies shoot me, the ally's follow me after I hit the right button but do not shoot at all. Am I using the correct scripts for 1.17 dark AI?

Anyone have an ideas what I'm doing wrong in both cases.

Thanks everyone
raymondlee306
16
Years of Service
User Offline
Joined: 24th Oct 2009
Location: Ohio
Posted: 10th Sep 2010 01:14 Edited at: 10th Sep 2010 01:14
Ok, I'm just doing a complete remove program and delete of the program then a fresh install for the first problem, and I'm post the problem with the Dark AI in the scripts forum. Mod's please feel free to close this thread, the problem must be with my configuration.
zizidiot
16
Years of Service
User Offline
Joined: 17th Jun 2010
Location:
Posted: 17th Nov 2010 20:43
i can answer the first question on how to turn off bloom for good.
1.) close fpsc completely.
2.) open the setup.ini in notepad.
3.) change post processing to 0.
4.) close it and save it.
5.) then run the fpsc cleaner.
6.) if you wait for it to finish then open fpsc it should be gone .

zizidiot productions

Login to post a reply

Server time is: 2026-07-03 14:40:26
Your offset time is: 2026-07-03 14:40:26