KnightHawk75
Posts: 1450
Joined: 11/15/2018
Status: offline
|
So did 48 starts with different power management settings:
1 2 3 4 5 6 7 8 9 10 11 12
2ghz locked n n n n n n n n n n n n
3ghz locked n x x* n n n n x* n n n x*
1.6-3ghz flux allowed n n n n n n n n n n n n
2.0-3ghz flux allowed n n n n n n n n n x n x**
All were done in windowed mode, after pressing > screen was minimized.
60-120second wait between each restart, where applicable to verify proc was leveled down to 1.6 or 2.0ghz
All tests monitored after startup and pressing go procs were all at 3.06ghz throughout the test run duration.
n indicates normal (no problem instance)
x indicates runs where it happened as I've past experienced it (lots of crashes in roughly same places).
* indicates runs where it happened but not as past experienced, got a 1 single crash about ~25nm out from target. might be same result thewood was getting perhaps.
** indicates runs where it happened as I've past experienced, but I may have ruined the purity of the run being equal to the others by having a mp4 playing in vlc before\during exe startup, and loaded op's scene first before my own testrig, I doubt it mattered but wanted to note it (I simply forgot I wasn't done yet).
I don't see any consistency out of it all.
Yesterday I did bunch of testing on one "triggered" instance as it relates to 20-60E 40-90N.
Did a mix of firing from with-in it to somewhere inside it, partially in it (inside lat outside lon), from outside to somewhere with-in, outside to somewhere outside, and a couple inside-outs.
A smattering of screens from those runs.
I start with my usual "testrig" version run ensuring things are in screwy mode. I get the usual results from a launch from inside lat, to inside lat|lon.
4 shots from east of 60E but inside 40-90N.
The first screen is for context for the zoomed other 3 and shows run1 results (most north run).
These all had crashes shortly after crossing 60E, did not cross water or negative territory that I know of in latter 3.
   
This guy was fired from outside the suspect lat|lon, involved water and had crashes, though not shortly after.
Same target from inside suspect lat| outside lon, involved water and had NO crashes, one of the most unexpected results and goes toward disproving lat|lon theory.
Same target from outside long,inside lat, lots of crashes and quickly, but not near a "line" so to speak.
Same target ... just a little further north to take the alps out of it, basically same result.
Same target ... just a little further north to add water to it, crashes but hardly similar.
Same target from outside lat and long, crashes start after crossover on land, water involved.
Target moved outside long,inside lat. fired on from outside lat|long, water involved, crashes north of 40N.
Same target ...same firing pt, slightly different path, basically same result shortly after landfal > 40N mass crashes.
Target moved outside of both long and lat... fired on from outside lat|lon, water involved, zero crashes.
Now for a little something different
Inside lat|long firing on something outside lon but inside lat... water involved, mass crashes.
(Missing screen shot, I did one from fully inside to one fully outside and got crashes in spots inside... forgot to snap pic on that one)
For this one I did two firing units (clones), both firing form outside long, but inside lat,one at target inside 60L one outside 60L. both paths involve at least some momentary water. kinda interesting one gets lots of crashes one gets none.
Here we have the same two units firing from outside E20-60 N40-90 at something inside, lots of crashes.
The path might seem slight off cause I moved the target slightly to put more land in front of it just after launch but assure you outside the range ring those are crashes and not destruction(s).
 
Moving on to random other area where we fire from outside lat|long, at two targets, one inside lat, one outside lat. crashs on the inside one.
Here we have two launches one from both inside lat but not long,one outside lat and long, toward one inside, no water... no crashes. ???
Again seems one for the disprove column as it bucked the trend.
For giggle I re-ran that one again moving the target such that water had to be crossed.
I also slight moved the target back more into land shortly after launch as I had it literally on the coast which defeated the purpose of what I wanted to see (if water ie negative elevation cross-over made a difference). It definitely seemed too get a different result.
I did a couple sanity check runs across the USA\CA, and Africa, no crashes. no screens cause it wasn't any different than previously mentioned.
What does any of this mean, hard for me to say exactly. Hopefully it gives an idea of why I brought up that tile even if I think 2 of these screen shots argue against it being involved. Thought then it might just be crossing negative elevation, but then other screen disprove that so stumped again. 
< Message edited by KnightHawk75 -- 2/3/2021 12:56:50 PM >
|
Printable Version
RE: [Logged] Crashing JASSM & JASSM-ER - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread