Jump to content
Sign in to follow this  
quicksilver67

Need some help with a Xeno scenario...

Recommended Posts

So I really, really, really want to turn off the 'volumetric' clouds that pop up all over the Domination scenarios. The problem is one of complexity; Xeno is known for having difficult to edit scenarios, partially because things are in several places, or are hard to find at all. I can't seem to contact him, so the question is: where did he hide the code for the damned volumetric clouds. I've tried his weather options, but I can't find a randomly generated particle source; I've looked through folders and files, the inits for server and otherwise, but either I'm completely missing it (entirely possible), or he's referencing something I don't understand. Any ideas, anyone?

Share this post


Link to post
Share on other sites
The problem is one of complexity; Xeno is known for having difficult to edit scenarios, partially because things are in several places, or are hard to find at all.

Uh, it's just simple, easy and boring scripting...

where did he hide the code for the damned volumetric clouds.

As particle bla bla is something you only need on the client side... I give you a hint (the only sqs script Domina starts):

// brrr, sqs
[] exec "\ca\modules\Clouds\data\scripts\BIS_CloudSystem.sqs"; 

Xeno

Share this post


Link to post
Share on other sites

Thanks for the response Xeno. I tried to get in touch via a webpage addy I found on Armaholics, but it wouldn't load. I know what the execute line should look like, but could you please be a little more location specific?

I can't find it in the init.sqf, the i_server.sqf, the i_client.sqf, or the i_common.sqf; nor can I seem to find the line in the macros or setup files. I really expected it to be in the main init.sqf file, or with an includes line referring to an fsm file. I checked the mission.sqm file, just in case, since I have seen it put down on the map as a module. I've run a text search for the exec line, but that draws a blank, too.

I suppose I could always pop the file out of the ca folder to cause an error and then track the error, but that seems silly and time consuming.

Simple, easy, boring scripting, huh? From my point of view, compared to Benny's scenarios, your stuff is pretty complex, not necessarily in terms of what it does, but rather where it is.

Thanks for any help you care to provide, and thanks for the killer scenarios.

Edited by quicksilver67

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×