My program evaluates 30 frames per second and in doing so, it creates an array for a bitmap that holds 300,000 pixels (so for each frame iteration, it iterates through the 300,000 pixels). It's implied that I don't have much computational time to evaluate each frame without crashing my program.
Originally, I was intending on evaluating every pixel for every frame iteration, but I'm thinking a series of designated "hotspots" would be much more feasible. I would like to equally spread out designated hotspot pixels to tell me the distance from that pixel and this will cut down 300k checks to a few hundred at most. Calculations are based on how far away an object is and the Distance value in the textbox is the real-time distance away in millimeters. I then calculate the danger level based on how far away an object is from the hotspot. I think this will open up a lot of flexibility and allow me to have different danger values for different sub-sections of each frame iteration. For example, objects directly behind the vehicle can be given more attention than objects above or to the side.
Originally, I was intending on evaluating every pixel for every frame iteration, but I'm thinking a series of designated "hotspots" would be much more feasible. I would like to equally spread out designated hotspot pixels to tell me the distance from that pixel and this will cut down 300k checks to a few hundred at most. Calculations are based on how far away an object is and the Distance value in the textbox is the real-time distance away in millimeters. I then calculate the danger level based on how far away an object is from the hotspot. I think this will open up a lot of flexibility and allow me to have different danger values for different sub-sections of each frame iteration. For example, objects directly behind the vehicle can be given more attention than objects above or to the side.