Re: Current Post Processing support

>
> Note that it depends on what syntax was wrong whether that's expected
> behavior or not. If all the weaving syntax, etc. is correct and the
> shader simply fails to compile/link due to some problem with that it's
> expected behavior that this error is not detected at that point as
> evaluating whether a shader compiles/links is only done upon
> encountering the usage of that shader with a specific technique
> actually using the snippet in question. Accordingly (due to the
> delayed compile/link) you won't be guaranteed on load that the loaded
> shader will actually work as expected.

The sintax problem I referred is in the cg code, as you said it is compiled
only on first time usage but I think it should have a way to force the
 compilation  or at least have some error report when it is used

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr

_______________________________________________
Crystal-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/crystal-develop