blingthinger

Just me? No it's very clearly stated in the interview. I assumed everyone sifting through this thread would have also read the article in the OP link. My bad. "Moving into payware is obviously a big step. Was that a difficult decision for you? ... we are not exactly “selling” the product. We are simply asking for a small download fee to cover our costs and to help keep the other downloads free. It is more or less a form of donationware...."

In the reference I quoted you were very clear that it caused a slight issue for YOU. There was no reference to other potential buyers. So yes, that is exactly what you said. You need not fear for other customers' reactions, though I'm sure he's grateful for your good intentions and concerns. He's not offering this as a product with the intent to earn revenue. He's merely covering server costs with the fees. He very literally does not care if people buy it or not. Hahaha yeah that word doesn't mean what you clearly think it means, but hey, some folks proactively chose to be insulted regardless of the interaction....

"Issue" meaning that you absolutely will not be buying the Pro version? As in... your eyes are generally unable to de-focus from the blurry ortho that almost nobody actually ever sees (unless they run on 10 yr old hardware or laptops) and re-focus on the autogen buildings and their textures (the actual product in question)? You sat there staring, screaming a little bit inside your own mind? I too noticed the blurry textures. I thought, "at that altitude the XP default textures probably look better", but I can't say that it triggered any "issue"-like response. Certainly not to the level of balking at the actual product.

There's no intent to actively sell or market this. He's not even proactively looking for kindness tips. Just looking to cover server costs. He doesn't care one bit what the terrain textures look like in any "promo" video or if anyone doesn't download it. A true hobbyist.

You must have another layer injecting it somewhere. Deleting 1400 and 1401 removed all the airport vehicles on my install.

If sigma is the primary knob it's turning to tweak Dryden's equations, it's going to remain pretty close to what IRL data sometimes looks like. Spectrum plots in Fig 7 look pretty darn similar to the polynomial equations that Dryden came up with. https://agupubs.onlinelibrary.wiley.com/doi/full/10.1029/2022JD037491

And what happens after that? If that statement was all there is to it, there would be no need for iterating on feel for each acft. Pending clearer descriptions, you're saying that 8.3% of apples are oranges. Not a matter of "good enough". It's simply not using Dryden. Maybe starting there to some degree but the model itself appears to get smeared away based on what you're describing. It's a good starting point to "feel" better, but "feel" isn't "apply" as you've been claiming. LR wouldn't need to implement it internally for manual weather mode. I mean...that's exactly why the MIL document is bringing it up: to set a standard for flight simulators. The algorithm would have to calculate more accurate forces using the turbulent velocities and some basic geometry definition (fuselage areas, force coefficients, much like XP already calculates wing forces) but it's a complete model as is.

Very nice. Silence on the other question though...there's some scaling or morphing of the spectra curves happening somewhere. Question is if it's a linear shift or a scale factor and if it's uniform to the full spectrum. The reason I asked about L and sigma is because that's what's setting the spectrum shape at a given altitude. Depending on how it's being scaled or shifted, you might still be able to claim that it's using the Dryden model. Your silence is worrying there. It might be starting with Dryden sure, but if it's then morphing the model beyond recognition simply because you ran an iteration on a plane and say 'this doesn't feel right', and it wrings the curves out of shape, it's suddenly no longer Dryden. If you're maintaining the spectrum slopes and therefore energy dissipation into the higher wavenumbers/frequencies, your claim holds water. Otherwise, I currently don't see how you can claim that it's using Dryden.

So everything except turbulence eddy velocity delta, which isn't an option because it isn't provided by the sim. That's comparing apples to oranges. The amplitudes will be all manner of mismatched and I couldn't consider that by itself an implementation of Dryden's model. So where is Dryden's model still entering the picture? What values of length scale and intensity are used? Is it using a single value for each? If yes, that would certainly be a pity given that the report offers full up atmospheric distributions for both values. This must be where it's using a transfer function somehow. Had to do my own LLM search on this bit as I've never needed to actively alter a real-time signal IRL.

Behavior of which variables? Which physical datarefs are being compared to Dryden's spectrum curve fits? Per MIL-STD-1797, the model's outputs are the amplitudes of velocity oscillation of a passing turbulent eddy in one of the 3 Cartesian directions: vx (or y or z), at a given frequency in the modeled spectrum for that component. I'm surprised to see you using terms like "filter" or "transfer function" or iterative training of an acft model, given that they are neither found nor implied in the report. Appears that you ran into the same brick wall I did on this one. I couldn't find a way to turn it off either. Same question as above. How what responds? Which datarefs is it monitoring?

What variables is it using to make this match? E.g. local_y? local_vy? Normal force? Please do elaborate on what you've interpreted these specifications to be.

amd's catching up in the raytracing. Slowly. Gradually. Most of the reputation for problems with anything proprietary in the mix is the fact that none of the most popular distros from a decade ago were rolling releases. This meant you were stuck on a specific generation of nvidia driver for a year or more until the new distro release happened. If an app (e.g. XP in my case) demanded a specific version of driver that Debian happened to not offer yet, you had to go the manual route and that sometimes caused compatibility problems. Most folks never had to deal with the real issues nvidia caused. Linus' famous middle-finger-event happened because they were being a pain in kernel dev space. User space never really had to deal with that fallout because Linus worked around it. Hence the middle finger. The reputation propagated because it's opensource world.

Yes it continues to be quite impressive to watch and see what these LLMs are capable of with appropriate prompts and interactions.

Booo. I'm not aiming negativity at you and you know it. You "signed off" of the discussion a long time ago without answering any of my algorithm questions which were never worded negatively. You were immediately bizarrely defensive against a perfectly normal query into how you wrote the code. Any reticence to suddenly embrace your reappearance and gleefully ask more questions is 100% your fault, especially since you insist on misunderstanding my points above as negative. That said, is that even necessary at this point? Is there anything still "broken" in your eyes? It sounds like you have it fixed, no? It sounded like the LLM addressed your OP point before you even asked it (which is good because it means you don't trust it 100%). If it's fixed now then all good. I'll possibly peruse your lua after you post it.

Then you misunderstand that my tone is, for the most part, not directed at you. I don't like contention either. However I do even more dislike intentional misinformation and misdirection. Why did you paste such a huge wall of text in your initial responses? Because you felt like someone was calling you out as a fraud? Because you know that this ai topic IS a hot one right now? Maybe some of both? There are entire websites and companies and organizations fully banning ai-generated content. A lotttttt of people are furious about This. Very. Situation. One that you (hopefully accidentally) think is no big deal. So my only tone to you on this topic is: it is kind of a big deal. If you're going to be posting on a public website (hobby or not) in the future, be aware that they way you treated it is going to raise eyebrows. I personally don't give a hoot if you are LLM'ing your code or not. I probed for clarification because these days there is one thing worse than not reading the report: reading it and not understanding it and then making a technical and emotional mess of the model implementation in a public forum. If I know you're LLM'ing most of it, I can phrase things in way that won't accidentally make you look like the south end of a north-bound horse. If you find an error, everyone can chuckle that the ai is a word not allowed sometimes and move on because "haha sometimes they do that glad it was found before it was released to the public". Why didn't you clarify something like this at the start!!? Don't get me wrong. I have questions/doubts about exactly which data and what the LLM is doing with the data, but seriously??....you gave off all manner of tone and reaction that trained technical professionals have... no interest in engaging with.