A Community discussion forum for Halo Custom Edition, Halo 2 Vista, Portal and Halo Machinima

Home  Search Register  Login Member ListRecent Posts
  
 
»Forums Index »Halo Custom Edition (Bungie/Gearbox) »Halo CE Technical / Map Design »TSC:E Putting VISR script from player_bonus_test into my own .scenario

Author Topic: TSC:E Putting VISR script from player_bonus_test into my own .scenario (4 messages, Page 1 of 1)
Moderators: Dennis

ziko
Joined: Feb 26, 2011

Raw!


Posted: Jun 12, 2015 02:00 AM    Msg. 1 of 4       
Hey Guys, I was wondering if some one could help me out regarding putting the VISR script from tsc:e into my own map. I was wondering how exactly i can integrate the VISR script from the cmt_b30_evolved_source_release_scenario 'script' files into my own scenario/map

I have nothing written/scripted in my Equip_test scripts.hsc file as i am unsure what to exactly place in the script to get the VISR working!( I AM A NOOB!)

I've tried to follow the cmt_b30_evolved_source_release_scenario tutorial but i am unsure of how to connect the .hsh and .hs into the primary script .hsc of my scenario.

I am using notepad++ as well as the hspp file from halomaps.org to 'preprocess' my scripts.

Ive put the 'scripts' folder from the cmt_b30_evolved_source_release_scenario dir into my 'data' folder then inside that folder into my Equip_test(scenario name) folder.

this might sound a little confusing i'll try to send a screen shot of how it is setup!

I've also renamed all the 'TEST' and 'test' text in the .hs/.hsh files inside the 'src' folder to my scenario name and aswell as the batch files that preprocess my script (Equip_test).

Whenever i try run hspp_Equip_test the batch file i have the following error:

The system cannot find the path specified
---------------------------------------------
script analysis
---------------------------------------------
/_components_apis.hs
stdin:1: error: cannot create output file

/_components_globals.hs
stdin:1: error: cannot create output file

/_components_shared.hs
stdin:1: error: cannot create output file

/_components_cmt.hs
stdin:1: error: cannot create output file

/_components_scenario.hs
stdin:1: error: cannot create output file

IOerror: [Errono 2] No such file or directory: 'out/scenarios/test/main/__components_apis.hsc'
----------------------------------------
script analysis
----------------------------------------
the system cannot find the path specified
..done!

I wish i could send a picture of my directory setup but i dont know how to on these forums!

If anyone could give me a solution or send me a pic of how my directory should be setup in order to get the VISR script working would be much appreciated!

Thanks Ziko


FtDSpartn
Joined: May 1, 2009

Verified AI.


Posted: Jun 12, 2015 12:17 PM    Msg. 2 of 4       
Currently typing up a reply to your PM, should be done in a bit. I'll also paste it here for anyone interested, and if any CMT Evolved team members want to show me a shortcut in the process perhaps.

Edit: http://forum.halomaps.org/index.cfm%3Fpage=topic&topicID=48362
Edited by FtDSpartn on Jun 12, 2015 at 03:30 PM


Nickster5000
Joined: Dec 11, 2010


Posted: Jun 17, 2015 02:35 AM    Msg. 3 of 4       
If you don't want to work with TSC:E's new system (I eventually want to, but I am not to that level yet) I have my VISR script that I created for Sector 09. Haven't finished commenting it yet, but you may find it helpful:

;VISR SCRIPTS===================================================================================================================
(global boolean visr false)
;this determines if VISR is on or off.
(global boolean flashlight_state false)
;This determines the flashlight state.
(global boolean visr_needs_to_toggle false)
;This determines if the VISR needs to toggle due to a flashlight state change.
(global boolean visr_state false)
;This determines the state of VISR.

;This script defines the player as "Player 0", so that you do not need to call for the player in every single command.
(script static unit player0
(unit (list_get (players) 0))
)
;This script ensures that the "print" commands will print. Used for debugging. Place ";" in front in order to redact this command.
(script startup 420
(set developer_mode 127)
)
;This is the command that is called to turn on the VISR.
(script static void visr_on
(print "Turning VISR ON!")
(sound_impulse_start "RZS_Halo\s9\assets\sounds\sfx\visr-on\visr-on" none 1)
(pp_set_effect_instance_fade 0 0 1 0.3)
(pp_set_effect_instance_active 0 1)
(set visr_state true)
)

(script static void visr_off
(print "Turning VISR OFF!")
(sound_impulse_start "RZS_Halo\s9\assets\sounds\sfx\visr-off\visr-off" none 1)
(pp_set_effect_instance_fade 0 1 0 0.25)
(pp_set_effect_instance_active 0 0)
(set visr_state false)
)

(script continuous flashlight_state_check
(if
(= (unit_get_current_flashlight_state (player0)) 1)
(begin
(set flashlight_state true)
(set visr true)
(if
(= visr_state false)
(set visr_needs_to_toggle true)
)
)
)
(if
(= (unit_get_current_flashlight_state (player0)) 0)
(begin
(set flashlight_state false)
(set visr false)
(if
(= visr_state true)
(set visr_needs_to_toggle true)
)
)
)
)
(script continuous visr_set
(if
(and
(= flashlight_state true)
(= visr true)
)
(begin
(if
(= visr_needs_to_toggle true)
(begin
(visr_on)
(set visr_needs_to_toggle false)
)
)
)
)
(if
(and
(= flashlight_state false)
(= visr false)
)
(begin
(if
(= visr_needs_to_toggle true)
(begin
(visr_off)
(set visr_needs_to_toggle false)
)
)
)

)
)


Hope this helps!


ziko
Joined: Feb 26, 2011

Raw!


Posted: Jun 17, 2015 02:44 AM    Msg. 4 of 4       
SAME POST IN http://forum.halomaps.org/index.cfm%3Fpage=topic&topicID=48362

Hey dude thanks for getting back to me and uploading a tutorial about this!

But i am still suffering issues after following all your steps in the tutorial.

I am suffering errors when compiling the scripts in OS_sapien which is preventing me to create my .map file, Im sure it is an issue between the 5 .hsc scripts in my 'data/levels/EQUIPTEST/scripts' folder , i have a feeling that there conflicting with eachother.

###NOTES###

#I have enabled the VISR script in the cmt_features file located in my 'MFOLDER' and then ran the batch file.

#I have placed the armor_module VISR in my map but i cannot equip or use it. :(

#I have already followed your tutorials including: Installing, Folder and File Creation, File Editing / Find-Replacing, Preprocessing, Level Globals, Sapien Prep and Armor Abilities (Modules?)

###Steps I followed to try get it working!###

I compiled the scripts with my hssp_EQUIPTEST.bat file and received the 'out' folder that contains 5 hsc files ( __components_apis, _components_cmt,_components_globals, _components_scenario and _components_shared).

I then copied these files from the 'MFOLDER' <- (This files on the desktop) into my halo directory 'data/levels/EQUIPTEST/scripts' folder.

I also have my pre-exsisting scripts.hsc file in the 'data/levels/EQUIPTEST/scripts' folder for my map to run!

I then opened my .scenario file in OS_Sapien and tried to compile the scripts but I receive the following error ' bellow.

debug.txt from OS_Sapien

06.17.15 16:17:08 sapien pc 01.00.09.0620 ----------------------------------------------
06.17.15 16:17:08 reference function: _write_to_error_file
06.17.15 16:17:08 reference address: 401b13
06.17.15 16:17:08 CreateDevice succeeded with refresh rate = 0
06.17.15 16:17:08 Sound card doesn't meet minimum hardware requirements. Disabling hardware option.
06.17.15 16:17:12 Increasing sound decompression buffer size to 1048576 bytes

06.17.15 16:22:28 [_components_cmt line 29] there is already a variable by this name.: curr_player_weapon_type none)

06.17.15 16:22:28 [_components_scenario line 29] there is already a variable by this name.: curr_player_weapon_type none)

06.17.15 16:22:28 [_components_shared line 48] there is already a variable by this name.: curr_player_weapon_type none)

06.17.15 16:22:28 recompiling scripts after scenarios were merged.
06.17.15 16:22:28 there is already a variable by this name.: curr_player_weapon_type none)

06.17.15 16:22:28 there is already a variable by this name.: curr_player_weapon_type none)

06.17.15 16:22:28 there is already a variable by this name.: curr_player_weapon_type none)

As previously stated i believe they are conflicting with eachother as i have noted out (;;) in Notepad++ the particular variable among the compiled .hsc files and that has worked but causes other multiple errors and conflict between the scripts!

I would really appreciate if you or anyone could provide me a solution to this! or telling me that i have done something wrong!

I really want the VISR feature in my map! Thanks Ziko

 

 
Previous Older Thread    Next newer Thread







Time: Thu January 19, 2023 1:43 AM 125 ms.
A Halo Maps Website