On 6/6/25 12:54, jr wrote:
> nightmares, I should not wonder..  will there be a "POV-Ray Yuqk option
> translate" ("Peyote" :-)) utility ?

:-) Yep. Pretty much every day working on this I feel like quitting 
again. But, I cannot shake that an options re-work needs to happen for 
v4 and the game I want to personally play, so I'm trying hard to push 
through to something 'new-working' this time around.

As for auto-translators I have thought about them, but more in the 
context of all the SDL changes I've made than with these options changes.

Those using the shipped vim highlighting will have an idea about most of 
what is now in error new or so on in SDL, but of course not everyone 
uses vim. Plus, I couldn't figure out how to get the (non-language 
based) syntax checking to flag certain things reliably.

My POV-Ray option sets are relatively small 10 or less - a page or two 
at most - so I think updates should mostly be quick with the new code 
telling me what to do. Do other have really huge option sets for some 
reason I missed?

The moves of the photon and radiosity block settings from the parser to 
options parsing will be more work, but also pretty much one for one by 
name(*). With these settings in options I guess the option sets will be 
larger as used, though, I hope in the end people will just be able to 
mostly reference different, say, radiosity quality levels by pre-shipped 
file settings.

Aside: One thing I should have mentioned is all of the different _level 
settings could be combined into two (one each for message/trouble). 
There are a bunch of them currently because it helps me while developing 
to be able to look at things by sets / types.

Bill P.

(*) - Expect some around long enough to know some the radiosity settings 
will be moving back into the options stage where they were initially.

Post a reply to this message