Difference between revisions of "Papyrus FAQs"
added Troubleshooting section
imported>Digitalparanoid |
imported>Digitalparanoid (added Troubleshooting section) |
||
| Line 362: | Line 362: | ||
a function on your script in return to give the value back. The big advantage of custom | a function on your script in return to give the value back. The big advantage of custom | ||
events is they can dispatch in parallel, greatly speeding up processing. | events is they can dispatch in parallel, greatly speeding up processing. | ||
</pre> | |||
== Troubleshooting == | |||
=== What happens when Papyrus is "overloaded"? === | |||
According to SmkViper: | |||
<pre> | |||
The only thing "overloading" the script system will ever do will be to slow down all | |||
script processing. You could theoretically run your system out of memory at some point | |||
but the game would be unplayable long before then. | |||
</pre> | |||
=== Does Papyrus affect framerate? Or "drop" function calls? Or "lose" entire scripts? === | |||
No. According to SmkViper: | |||
<pre> | |||
Papyrus never affects framerate, nor does it "drop" function calls. It doesn't "drop | |||
scripts" either, whatever the heck that would mean) You wouldn't have an "overload" | |||
problem if it did, because then it would just throw things out instead of slow down, | |||
but that way lies madness - randomly not running function calls is just silly. | |||
</pre> | </pre> | ||