Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Test Builds => Topic started by: WMCoolmon on November 23, 2007, 06:19:57 pm
-
- FRED event editor updated (http://fs2source.warpcore.org/temp/wmc/new_event_editor.gif)
- Visible subsystem name can be changed through scripting; will not be changed in the log
- Added Asteroid, debris, and ship collision damage type support
- Added Asteroid, debris scripting collision handling
- Added Many, many additional Lua functions and variables
- Reinstated "Self" variable for HUD
- Added automatic drawString moving-to-next-line
- Standardized override order
- Fix the dreaded random-Lua-parse-crash bug
- Improved nonwindows Lua errors
- weapon_armed update
Release builds (http://fs2source.warpcore.org/exes/latest/C11232007.zip)
Debug builds (http://fs2source.warpcore.org/exes/latest/C11232007d.zip)
-
- FRED event editor updated (http://fs2source.warpcore.org/temp/wmc/new_event_editor.gif)
Ooooh.
-
what does the pop up error "failed to create the command recognition context" mean?
i get this in this build and that newer debug build you put out as well. i get this when running my rts script. it gives the error and it locks up the build.
its really odd, the build wont even run on vanilla data ever since i got that error.
-
what does the pop up error "failed to create the command recognition context" mean?
i get this in this build and that newer debug build you put out as well. i get this when running my rts script. it gives the error and it locks up the build.
its really odd, the build wont even run on vanilla data ever since i got that error.
Sounds like part of the speech recognition code.
-
yea thats it, disabling the feature seems to work for now.