Light settings

[[Cl...]]

Hello all. I want (need) to change the light settings for the camera between a two part family (PCM) program. I'm using PCM to swap out the models and nominals. The points I'm measuring with the camera have different Z values part to part. This causes subtle changes to the iplit setting. Can I use PCM to change this? If so how? I've tried a few things but no luck. Basically I need a second iplit setting for the other part.

O-inspect 543 CALYPSO 2020 , ServicePack 1
Version 7.0.0211 (17.12.2020) - Patch version

[[No...]]

I'm not aware of any PCM commands to set lighting (unless Eric or Israel come around the corner with some magic 😉 )
But you can set up an alternative strategy (you can even copy the existing strategy) and only change the light settings. Then use setElementStrategy() to switch between them.

[[Mi...]]

I would say Norbet is likely right, use the multiple strategy options, give both strategies meaningful names, then use PCM to select them, I do this with programs that are on completely different CMMs that have different stylus systems and even XT vs XXT, so scanning speed changes and all that, yours would be simpler as you would copy the strategy and just make your minor changes.

In my case below I'm making the selection based on the CMM serial number. You could likely use the setInspectionStrategy() in with your code that's already swapping out the models.

CMMNumber=getRecordHead("dmesn")
selectCase CMMNumber
	case "141450"
		setInspectionStrategy("141450")
	case "190416"
		setInspectionStrategy("190416/190417/281710")
endSelect

[[Cl...]]

I'm no PCM expert. I have a working knowledge of it, and use it primarily
for part family programs. Where is this code placed, in the feature?

[[Mi...]]

setInspectionStrategy() selects the strategy for the whole plan when you have multiple ones, as it sounds like you need to make, so it would go in your presettings for the plan... You say you're using PCM to change the model, how exactly are you doing that?

[[Cl...]]

clearCAD()
dir = getActualInspectionDir()

Part_Size = inquireList("Which size part would you like to run?", "Diameter_.1247", "Diameter_.0934")
selectCase Part_Size
case "Diameter_.1247"
loadCADFile(dir+"\.1247.sab")
case "Diameter_.0934"
loadCADFile(dir+"\.0934.sab")

endSelect

[[Mi...]]

So thats in the program presettings then, easy you would just add it to the case select you're already using. With one strategy for each part size. I just picked the names from the case select because it's nice when you use the same names everywhere, but name the strategies whatever you like, just make sure the name in setInspectionStrategy() matches your strategy names.

clearCAD()
dir = getActualInspectionDir()

Part_Size = inquireList("Which size part would you like to run?", "Diameter_.1247", "Diameter_.0934")
	selectCase Part_Size
		case "Diameter_.1247"
			loadCADFile(dir+"\.1247.sab")
			setInspectionStrategy("Diameter_.1247")
		case "Diameter_.0934"
			loadCADFile(dir+"\.0934.sab")
			setInspectionStrategy("Diameter_.0934")
	endSelect

This would work for the entire program, it's that way I would recommend to do it. But you could use setElementStrategy() instead for each feature in question... it really depends how many features you have to change.

[[Cl...]]

I have 12 points, so what ever is the easiest.

[[No...]]

I'd recommend setInspectionStrategy() (I had just forgotten this one exists 😉 )
Since you want to change all the light settings per part, there's no reason to use setElementStrategy().
The strategy name is just a name after all. You can still set different light settings in every feature under the same strategy name.

[[jh...]]

Please sign in to view this quote.

Next to lighting from the background and any object with an emission shader, lights are another way to add light into the scene. The difference is that they are not directly visible in the rendered image, and can be more easily managed as objects of their own type.

Common
Light settings for all renderers.

Cycles
Samples
For the branch path tracing integrator, this specifies the number of direct light samples per AA sample. Point lights might need only one sample, while area lights typically need more.

Max Bounces
Maximum number of times light from the light is allowed to Bounce. Limited by scene-wide bounce settings.

Cast Shadow
By disabling this option, light from lights will not be blocked by objects in between. This can speed up rendering by not having to trace rays to the light source.

Multiple Importance Sample
By default lights use only direct light sampling. For area lights and sharp glossy reflections, however, this can be noisy, and enabling this option will enable indirect light sampling to be used in addition to reduce noise.

Area Lights
Portals
Area lights can also function as light portals to help sample the environment light, and significantly reduce noise in interior scenes. Note that rendering with portals is usually slower, but as it converges more quickly, less samples are required.

Light portals work by enabling the Portal option, and placing areas lights in windows, door openings, and any place where light will enter the interior.

In outdoor scenes most rays do not bounce much and just fly off into the sky and therefore, light portals are not helpful for outdoor scenes.http://myaccountaccess.live/http://krog ... ack.today/