Suitability Modeler Scale Miscalculations

[Kyralai]

I am creating a suitability model with 3 layers. When I add all three layers, one of them throws off the suitability scale to make a scale of extremely low and inaccurate values. I had this issue another time as well when I added a layer and it threw the scale into negative values. When I remove that layer, the full resolution map only shows for a portion of the area which I specified the processing to be in (maybe the areas where both of those layers overlap?). I need to be able to see results for all of the areas where there is input data so I had the processing extent set to reflect that. All of the layers were made with polygon to raster and the settings for cell size, coordinate system, and extent were the same. The input raster layers also all appear normal on the map. Has anyone run into this problem with the scale being thrown into incorrect low or negative values and know what the cause is?

[SteveLynch]

The crux of this issue is that the one criterion has data in the eastern part and NoData in the western part. The other criterion has the opposite, viz., NoData in the eastern part and data in the western part. When combining the two criteria the suitability map map is filled with NoData and the default renderer shows very small values. Suitability Modeler is doing what it is designed to do.