I'm not ignoring your point, but you seem to be ignoring mine. The "built-in" circuit (not comparator) hysteresis (yes, I noticed the name) is provided by the lag of the output LC filter as I previously noted. You can add some hysteresis to the comparator to minimize oscillations in the comparator due to local feedback but it's not needed for the intrinsic operation of this hysteretic converter. The simulator is not "LYING". The circuit does work as shown (albeit with some ideal characteristics).Hysteretics have "built in" hysteresis (notice the name?) in the comparator to keep the thing from endlessly chattering. It's one of the main disadvantages of a hyst design, since it's output voltage ripple is higher due to the fact the output goes up and down a specific amount of voltage between the design set points where the oscillator turns on (Vlow) and shuts off (Vhigh).
I think you are ignoring my point of posting: IMHO the circuit as shown won't work, and it's ridiculous when a simulator shows performance data for a circuit that can't work since it is LYING and telling the user it does work. The schematic doesn't even include a pull-up resistor to turn off the switching transistor. As I said: if you think that dog can run, build it up. Then when you get it working, post the final schematic and compare to the one posted in the OP.
The comparator in the schematic has a push-pull output drive so it doesn't necessarily need a pull-up resistor. (But the simulation doesn't show that the comparator would likely blow with 12V applied so that is a definite simulator limitation).
You can say the dog can't run but you give no reason other than saying so. You'll have to pardon my lack of agreement.
I don't really have time to build a circuit to prove a point, and even if I did and it worked, I'm sure you'd find some reason to show how it's an exception to your rule that simulators lie.
What good did simulating do? Simulating showed that the circuit will fundamentally work. It can save a lot of initial design errors and help develop the design parameters and explore design margins. Then you tweak the final design with the breadboard.It's true Bob and I were skeptical of sims, and with good reason: we kept running into a whole batch of idiots who use them as a crutch. Our customers used sims to leapfrog the design phase and then howled when their crap didn't work. No person should ever be allowed to use a sim unless and until they are experienced enough to know where the sim is lying. That sentence can not be emphasized enough. Even some of our "best" designers fell into the lazy trap and got burned using sims for IC design. The so-called best models don't work in many cases and designers get bit.
..............................
In this thread, the problem is pretty clear: the OP doesn't know enough about a buck converter to know where the power losses are and is using a sim to give performance data. I don't see that as helpful.
Then exactly what good did simulating it do? The "data" from the sim can't be taken as accurate, you still have to take real data. The design is not accurate, you still have to make it work. The designer should read an app note, build the circuit, modify until performance is correct, then they are done. In the process they gain the understanding of how it actually works.
.............................
You are sour on simulation because you had experience with a bunch of idiots who don't know how to properly use a good tool so you throw the tool out with the bath water. Better to educate the idiots about how to properly use the tool.
But I understand I'm beating a dead horse here. You don't find simulators useful and I do. So I guess we'll have to let it go at that.