Started by Diggis, March 05, 2009, 02:20:44 PM
0 Members and 1 Guest are viewing this topic.
Quote from: Chrisadams3997 on May 05, 2009, 05:13:11 PMI'm actually curious what the fix you've mentioned is, but this isn't a development thread, we'll need to open a new one or continue an existing one(let's keep it on SC4D, I hate trying to post on Simtrop).
QuoteI would also like to exchange some ideas with you about reintegration into one development and compatibility with MR3.6+]
fn FnEnableNightLigts shine =( if ($lights.count > 0) do -- scene has local lights ( if not shine then --turning nitelites off ( --array to save nitelites that are on only, to be turned back on later gNiteLiteOn = #() --only "nitelites", remove spot targets, and only those presently turned on for lt in $lights where (substring lt.name 1 8) == "nitelite" and lt.classID != 4128 and lt.on == true do ( --save them to array append gNiteLiteon lt --turn off the nitelites lt.on = false ) ) else --turning back on ( --remove any lights from array potentially removed after nitelites where turned off for lt in gNiteLiteon where (isdeleted lt or lt == undefined) do deleteitem gNiteLiteon lt --turn on the nitelites that were on before for lt in gNiteLiteon where lt.classID != 4128 do lt.on = true ) ) )
Quote from: SimFox on May 08, 2009, 03:56:52 AMCallagrafx:I didn't say anything because the only thing that I could have said quickly and definitively at the time would have been - don't use this version of Bat4max! It's author is missing, I myself see a lot of, what I perceive as, inconsistencies and excessive coding in script because of which it is a very difficult to find a way around, and the people who release it have no experience, knowledge needed to provide any kind of meaningful support for such a tool. Because support for such a tool is not telling people what button to press, but ability to fix some errors in code that may and will resurface. Even if I wouldn't have been able to fix one function, and I really mean fix this function not simply replace it with mine, it would have taken me a lot of time and sort of made liable to continue provide support, e.g. basically doing your "job". Problem is that I'm not familiar with internal logic of the whole thing... It's just not time efficient. And giving simple indication of where in the script the problem in question starts wouldn't do you any good, now would it? So there was this dilemma...Now since the Chris is back situation is radically different. I know I don't need to go and simply redo the thing. It would be sufficient to simply point to the spot...And so I'll proceed to the task at hand:
Quote from: SimFox on May 05, 2009, 02:10:54 PMYou're right though that it is easy to fix. All it takes is to take one word in a script... And since you're back now i hope you'll do it.
Quote from: SimFox on May 08, 2009, 03:56:52 AMCallagrafx:I didn't say anything because the only thing that I could have said quickly and definitively at the time would have been - don't use this version of Bat4max!
Page created in 0.059 seconds with 30 queries.