Squiffy

Yes! +1

"Ja, der geist spricht..." :D or on another tack 饮用水时考虑来源

:D "Churches!, Lead!, Very small rocks!" :D Thanks, I needed that. And sorry for the rant. Yeah copyright gets a bit confusing, especially dealing with fair use and production and I wasn't clear about that in my first post. And it really is too hot up here. 95F at Norwood airport and my reading room at work under the skylight is 82F Built in 1898. :(

This is why I said not to sweat it. It will likely be very difficult to get a "cease and desist" order over there. Call me defensive, but as far as "comprehension" goes, broken English and Chinese "Twitterati" is not exactly my idea of scholarly writing, but what would I know?, I'm only a librarian. Yes the main complaint may be about video production and publication, but is not the same concern as the code itself and true "copyright" license. It's not entirely clear from the sandwiched screenshots and misuse of the term "copyright" what act they were referring to? [(P) is used for production] Especially the one shot from a YouTube video with DCS and HeatBlur in the title. The line in the license agreement could be improved. Sorry to ruin your day with any distractions or apparent "comprehension" issues. I stopped worrying about that after I took the GRE and then postgraduate classes after my masters. Some people can't write their way out of a paper bag. We all deal with language issues on this international forum and don't call out "comprehension." No offense to ESL members. I do care about the license agreement and hope this can be dealt with. I am not denying the value of that at all. I just have my suspicions and think it's not as serious as all out piracy of the sim code and installation. Rant off, it's too hot in New England right now ;)

"Crackle crackle, burn burn!" :D I wouldn't sweat it too much at this point guys. It looks like they have only gotten a hold of the main package and some planes. They may have even bought them outright but are making videos in the meantime. They are clearly trying to claim it as their own but the integrity checks should account for all of this. There may be a hole somewhere that they hacked through but I have faith ED and FC can close it if needed. With this in mind, be careful as you pursue this and don't get hooked in a phishing scheme. That could be what is motivating this aside from real fan frenzy over there. "What else floats on water?" :D

Just happened again. Had to dig to find the log AND track file I KNEW I saved. It was in Open Beta under saved games of course ;) I did 2 updates since last post as well. Replaced my edited F-86, MiG-15 and Shell_table.luas Sound loss is towards the end of each track. sound loss 1.trk sound loss 2.trk dcs.log.txt

This would be the TR-1 no? And F10 map? I just want one that holds the same zoom as the last time I looked.

Do we know what was causing this? I wonder if it is related to the splintering fractal rays emanating from the cockpit center after ejection? It happens on all aircraft I think, not after canopy jettison, only after ejection. It's kinda weird like a model leak or vertex problem. Oh, I see the note about LODs. Thanks, still curious about the ejection issue.

I flew last night, saw another update, declined and just had some dogfights. Sound in the cockpit is different when taxiing back with the canopy open. I did not create any log file in the autoexec.lua. Not sure how that would work and I want to see if is was already fixed in the last couple updates.

I may have found it. Is it autoexec.lua? "Originally Posted by derelor View Post Just flew the bomb training mission several times without issues. You can try turning on extended logging by placing the following command - which should also work in release build - in your autoexec.cfg: (actually .lua) log.set_output("dcs", "", log.ALL, log.FULL)"

I still could not locate the autoexec.cfg file! I searched windows. Something is missing. I think there is an autoconfig.cfg in the DCS folder but I need to check tonight. It may be that the wing stress sound in cockpit for the Sabre causes a data error that wrecks the sound environment in the cockpit. Works fine from external view and with some other radio messages or the like. ... Maybe the "stess" sound file is actually missing and this causes the sound routine to crash from that "earpoint" location? I only saw a couple effects files in the sabre folder. G breath, wing load, but no actually tin can - spar stress sound. I would love to create a log but but I can't do that without the right file edits! This may be a moot point if the bug was finally fixed in the last update. Sounds seemed to change a bit but I saw no sign of it in the change logs so far.

Triple A glowing basketballs along a curving arc is about all you can expect to see. Tracers are about the same thing but smaller caliber. I saw no tracers to speak of at all in that video. It was mostly bombing runs and air frame thumps for bomb release.

I'm having trouble finding my autoexec.cfg file. Would someone point me in the right direction? I can search it of course but it wasn't in the DCS folder where I expected.

I will try the log scripts from the other thread and test this week. It MAY have been fixed with the latest Open Beta update. I noticed different sound dynamics internal and external views. Also, the wing overload sound may have something to do with it. That was mentioned a year or so ago and kinda was forgotten.

Hmm, I use it a lot, all air to air. In fact, the priority bias is kinda frustrating when you are in a furball and want to switch targets. You can clear it once or twice and try to select another but it keeps going back to the old target or toggle through in sequence to the remaining targets. It may just be that you have to clear it a couple times or wait for it to register. My buttons are programmed to the my old Cougar. Works fine there.

Don't forget to take into account reflected light. Depending on the surrounding colors, like trees or dirt, concrete or sky, the model will reflect light according to the rendering engine. Matte or gloss will have some effect but it should be subtle and not look like a moss or algae coating. To me gray-er is better.

In a maybe related question... does anyone know why the MiG-15 would be doing this after ejection? I am getting weird fractal ray like patterns from the cockpit after the canopy is jettisoned. External view of AI planes. Was fine before update that included rough met skins. The rays move around front and back kind of in a conical pattern from the one splinter point. Maybe it's my nVidia set up and game graphics settings but it looks like something in the Open Beta engine. I didn't change anything in my settings that I recall. Not sure if it happens with other models but maybe so. Like the Dora. AI Sabres may do it too.

Love the ripples and textured panels. Good job!

Thanks Jedra!

Thanks Rick, just chip away at them.

Awesome! "Please check the oil" ;) I got to fly on the 135 and 10 when I was in ROTC. Sitting or lying in the boom operators position was way cool. I don't remember if we got to fly it. Thanks for your input.

Did you burn enough or did you unstart with a compressor stall. Well modeled in the Sabre. You can emergency air start. Never paid much attention as I only have time for dogfight practice with newbie cheats on. (Fuel and ammo)

Cool! Love that wing and stars. Perfect.

I goofed a bit with the 131 versus the cannons. The barrel warp equations are 'slightly' different but still very close. Then I found these just today: https://www.northropgrumman.com/Capabilities/50CalAmmunition/Documents/M20FactSheet.pdf https://www.northropgrumman.com/Capabilities/50CalAmmunition/Documents/M33BallFactSheet.pdf

Nice! :D