SmokeyTheLung

Noted. Looking forward to the implementation from ED

Stumbled onto this short clip for those who are interested. Presumably relevant to IAT/MTT and possibly offset (notice that the crosshairs are not centered in the display) ?

Exactly. Reposting this report on "Temperature Measurement of a Bullet in Flight" here. Would be an awesome and realistic upgrade to the FLIR rendering tech. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7764414/

I've noticed that the rounds from the cannon are usually visible in RL FLIR footage but not so in the new DCS FLIR. I've also found this interesting article on the thermography of bullets in flight. Would be a cool and realistic addition, unless I'm missing something obvious. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7764414/

Waaaay back in the initial release of A10C Warthog (beta 1 I think) the digital zoom on the lightning resulted in really low resolution in all modes at extreme range, IIRC this was particularly pronounced in the FLIR modes, as they presumably simulated a lower resolution output for that sensor as compared to the CCD sensor in the pod. ED changed this quickly and explained that they felt the images were too degraded. My understanding was the math was correct on the initial version, the pixel count was correct and the digital zoom behaved as expected at long range; in other words the images looked like crap at really long ranges. As a side note: there was (as recently as four or five years ago) some vestiges of this original code commented out in one of the sensor .LUA files. I've never personally seen real TGP footage at these extreme ranges but it would certainly be interesting to see how crisp/clear of an image the sensors can create, presumably there is a lot of digital trickery in the real sensor processing to clean up images. It seems obvious that what the OP is seeing is a bug or engine limitation and I know my point is a bit OT, my apologies. However it would be interesting to know if ED is revisiting a more realistic TPod limitation for the Hornet and other new modules vis-à-vis digital zoom and it's real world limitations.

Thanks for sharing with us and for your service, samesies to all the other folks in the same category. I'm trying to make sense of the argument that's being had here. On one hand we have information about what the jet is capable of and on the other we have the hard won info on what the jet is "practically" capable of (I'm thankful that you and others take the time to share this perspective, for the record!). Is that right? ...or am I missing something? Practical may go out the window if things get hairy enough, I think we can all agree on that. What happens if the Canadians run out of maple syrup and bacon? They may very well plan a full scale invasion of the US, what would you hang from the wings in that case? DCS isn't simulating a USAF "practical, big picture, asset longevity, etc. etc." oriented simulation that would fit comfortably with the RL experience from you folks of the past 30 years. They are simulating an F-16. (emphasis on the period) Why not allow even the extreme possibilities of the platform in and leave it to us simmers to enjoy the game in whatever way we want? Joking aside, it's a genuine question. Is the jet capable? Even if it's completely unpractical?

Although it's not been totally clarified by Wags, it was cool to hear that the Maverick may be getting some seeker logic upgrades to make it more realistic; specifically the need to tell the maverick if you want to lock light on dark or hot on cold or vice versa. I have another suggestion that's really just visual but would help to "sell" our virtual version... at least in my opinion: Please see this video at around the 26 sec mark, played at .25 speed. You can see the the Maverick is in a slew state and attempts to find a hot on cold target. You can see just how much the crosshairs will move independent of the seeker gimbal in looking for a lock. In DCS this is represented by a pretty instantaneous snapping of both the seeker and tracking gate to the target. So it seems like DCS simulates a reasonable approximation of the function but could polish the visual a smidge. We have so much real world maverick footage in the public domain it seems like a shame to miss the small details (pointing cross anyone :D) like the wiggly jumping crosshairs. After seeing some of the detail work Heatblur have done with the F14 I'm obviously spoiled... and arguably also a total lunatic. Thought I'd leave this here anyway :)

Also, while I'm here... The details and effort already showcased are truly STUNNING. You guys had me at FLIR washout... :D

Just wanted to chime in and point out that all of this negative noise from a few folks is ultimately borne out of excitement to see and enjoy what you guys have worked to create. So that's at least a little silver lining, from my perspective. It's obvious to me and I expect most others here that you are considerate and professional artists/developers and are working HARD to push the needle further with as little comprise as is possible. I for one am blown away with what I've seen so far an am super excited. You can't rush it... well you probably could... but you don't seem the type... It will be done when it's done and I think 99.999% of your customers appreciate that breaking the mold in terms of quality will take time.

My guess is that only a particuarly low altitude delivery, with the aircraft level to the horizon and dumb bombs, will result in impressive accuracy in AUTO. From what I’ve seen, real pilots appear to fly profiles in AUTO/CCRP modes that are pretty similar to what most of us sim flyers use for CCIP; some amount of dive, velocity vector held steady at a point on the ground beyond the target that also coincides with the bomb fall line. Basically exactly like a dive delivery in CCIP but just in a different mode. I think the level high altitude delivery is probably mostly used for guided stuff irl. ...this is conjecture mind you and I’d be happy to be corrected.

In addition to what's been said: I'm pretty rusty these days but IIRC the TGP displays AGL altitude from the terrain database. You might be able to access that info in the CDU but I'm not sure.

Fair point and yes indeed, it's keeping me busy! Sent you a PM

Me too! Love DCS to bits but can't stop cringing when I see videos that show off all the great stuff added in the last few years along side the outdated effects. It's time!

Great to see some work done on this!

That puts that one to bed. Nice!

Yes, around there. Agreed as to the yaw but it's the opposite yaw then we see in DCS ...I think? It's been many months since I've flown the DCS P-51. It's also interesting that at 4:02 it's much more stable (at least to my eye). It would be amazing to find a pilot from those times and ask him!

Here's an interesting few clips. Unknown aircraft and weapons. As far as I can tell the pilot(s) are firing single rockets instead of pairs, which seems quite rare going by gun camera archives (it's sometimes hard to tell because of the placement of the gun camera). Maybe you can get some information from watching. Check out 4:02 and 2:43

Hey guys. My DCS doesn't want to open anymore after the last update. Nothing happens after the little CMD window closes. DCS is up to date, repaired several times, restarted the machine a few times too and I downloaded and installed the Microsoft stuff recommended in the sticky post above - I was told I'm up to date - you guys have any tips? Logs included, I tried deleting the file mentioned in the log and doing a repair but it didn't help Thanks! === Log opened UTC 2015-04-12 23:54:20 00000.000 INFO EDCORE: createSerialQueue IOQueue 00000.090 INFO VFS: Using 'Saved Games': "C:\Users\Julian\Saved Games" 00000.091 INFO DCS: DCS/1.2.16.37730 (x86_64; Windows/6.1.7601) 00000.097 INFO EDCORE: (dDispatcher)enterToState_:0 00000.102 INFO Dispatcher: 2015/4/12 16:54 V1411061313 00000.134 INFO INPUT: Device created Mouse 00000.134 INFO INPUT: Device created Keyboard 00000.147 INFO INPUT: Device created Joystick - HOTAS Warthog {DE4BE180-F7F4-11df-8002-444553540000} 00000.147 INFO INPUT: Joystick created[Joystick - HOTAS Warthog {DE4BE180-F7F4-11df-8002-444553540000}], ForceFeedBack: no 00000.151 INFO INPUT: Device created Throttle - HOTAS Warthog {5725F330-F7F4-11df-8001-444553540000} 00000.151 INFO INPUT: Joystick created[Throttle - HOTAS Warthog {5725F330-F7F4-11df-8001-444553540000}], ForceFeedBack: no 00000.310 INFO INPUT: Device created Saitek Pro Flight Combat Rudder Pedals {D2108390-225F-11e0-8001-444553540000} 00000.310 INFO INPUT: Joystick created[saitek Pro Flight Combat Rudder Pedals {D2108390-225F-11e0-8001-444553540000}], ForceFeedBack: no 00000.316 INFO NET: events.lua loaded 00000.317 WARNING LOG: 1 duplicate message(s) skipped. 00000.317 INFO NET: loading ./Scripts/net/default.cfg : OK 00000.317 INFO NET: loading C:\Users\Julian\Saved Games\DCS\Config/network.cfg : OK 00000.317 INFO NET: loading ./Scripts/net/net_types.lua : OK 00000.317 INFO NET: default_conn is 4 00000.431 INFO SOUND: loaded 944 sdefs from "sounds\sdef" 00000.436 INFO SOUND: XAudio2: Using device ID:'{0.0.0.00000000}.{d99b7385-7881-42e1-9824-9063784293bc}' Name:'Speakers (Logitech Wireless Headset)', channels: 2 00000.436 INFO SOUND: XAudio2: channel layout: Headphones/Stereo 00000.469 INFO SOUND: Using SSE FTZ/DAZ mode. 00000.673 UNKNOWN WinMain: MOD loading: ./CoreMods/aircraft/C-101/entry.lua 00000.674 UNKNOWN WinMain: MOD loading: ./CoreMods/aircraft/C-101/C-101.lua 00000.674 UNKNOWN WinMain: MOD loading: ./CoreMods/aircraft/C-101/Views.lua 00000.675 UNKNOWN WinMain: MOD loading: ./CoreMods/aircraft/F-86/entry.lua 00000.676 UNKNOWN WinMain: MOD loading: ./CoreMods/aircraft/F-86/F-86.lua 00000.676 UNKNOWN WinMain: MOD loading: ./CoreMods/aircraft/F-86/Views.lua 00000.677 UNKNOWN WinMain: MOD loading: ./CoreMods/aircraft/Hawk/entry.lua 00000.678 UNKNOWN WinMain: MOD loading: ./CoreMods/aircraft/Hawk/Hawk.lua 00000.678 UNKNOWN WinMain: MOD loading: ./CoreMods/aircraft/Hawk/Views.lua 00000.679 UNKNOWN WinMain: MOD loading: ./CoreMods/aircraft/MiG-15bis/entry.lua 00000.681 UNKNOWN WinMain: MOD loading: ./CoreMods/aircraft/MiG-15bis/MiG-15bis.lua 00000.682 UNKNOWN WinMain: MOD loading: ./CoreMods/aircraft/MiG-21BIS/entry.lua 00000.682 UNKNOWN WinMain: MOD loading: ./CoreMods/aircraft/MiG-21BIS/Entry/Aw 00000.685 UNKNOWN WinMain: MOD loading: ./CoreMods/aircraft/MiG-21BIS/Entry/Am 00000.686 UNKNOWN WinMain: MOD loading: ./CoreMods/aircraft/MQ-9 Reaper/entry.lua 00000.687 UNKNOWN WinMain: MOD loading: ./CoreMods/WWII Units/entry.lua 00000.688 UNKNOWN WinMain: MOD loading: ./CoreMods/WWII Units/Weapons.lua 00000.689 UNKNOWN WinMain: MOD loading: ./CoreMods/WWII Units/FW-190D9.lua 00000.689 UNKNOWN WinMain: MOD loading: ./CoreMods/WWII Units/Views.lua 00000.691 UNKNOWN WinMain: MOD loading: ./CoreMods/WWII Units/Bf-109K-4.lua 00000.691 UNKNOWN WinMain: MOD loading: ./CoreMods/WWII Units/Views.lua 00000.692 UNKNOWN WinMain: MOD loading: ./mods/tech/9p148.lua 00000.692 UNKNOWN WinMain: MOD loading: ./mods/tech/BRDM-1.lua 00000.693 UNKNOWN WinMain: MOD loading: ./mods/tech/CombinedArms/entry.lua 00000.693 UNKNOWN WinMain: MOD loading: ./mods/tech/D-30.lua 00000.694 UNKNOWN WinMain: MOD loading: ./mods/tech/Kraz-255.lua 00000.694 ERROR DCS: Error running \Scripts\server.lua: [string "Scripts/Database/scripts/utils.lua"]:31: bad argument #1 to 'pairs' (table expected, got nil) === Log closed.

sweet!

Apparently it's the way the real aircraft works (maybe this has changed with newer versions). A workaround is to slave your AIM-9 to the TGP, so the AIM-9 seeker symbol will be coincident with the TGP line of sight

If you're up for the challenge of sim mode, do it! It's a relatively simple (albeit quirky) airplane and it's quite rewarding to learn :)

Also, a mix of Kh-66 and S-24 will cause the same issue

You have to hit load all or load DSMS after the weapons are on your plane. So if you are using the load out you selected in the mission editor you shouldn't have this problem. If you are adjusting you load out via the re-arm menu you must wait until the stores are loaded, then use the Load page to tell the plane what you have. You may also be experiencing a bug which commonly occurs when the prepare mission function is used. Basically, once you select prepare mission in the editor your payload is "locked." If you used "prepare mission" you can fix the issue by unzipping the mission file and editing some code. I'll see if I can find you a link with instructions.

Correct

Scout