SmokeyTheLung

here's the juicy bit: 00045.058 WARNING LOG: 7 duplicate message(s) skipped. 00045.058 ERROR DXRENDERER: Transparency AA:, S_OK 00045.152 ERROR DXRENDERER: Can't create effect: postmotioneffect/nightvisiongoogle/nvd.fx. Reason: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Bazar\shaders\PostMotionEffect\NightVisionGoogle\nvd.fx(51,14): warning X3207: Initializer used on a global 'const' variable. This requires setting an external constant. If a literal is desired, use 'static const' instead. C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Bazar\shaders\PostMotionEffect\NightVisionGoogle\nvd.fx(73,10): error X1507: failed to open source file: './nvg_mod.hlsl' 00045.153 INFO DCS: try to write dump information 00045.735 INFO EDCORE: Minidump created. 00045.735 INFO DCS: try to write track file

:doh::doh: Okay, so I guess editing the graphics.lua is no longer necessary. Back to square one, here's the DCS.log: dcs log.zip

:doh: I've forgotten to edit the graphics.lua I'm guessing that's the issue, when I get I chance to try it again later today I'll report back. Thanks!

Has anyone one gotten this mod working in 1.2.8? I'm getting a crash when I try to use it and I'm pretty useless when it comes to .lua ty in advance!

:lol: Quote of the year!

Force correlate is one of two ways that the maverick can lock onto a target. In the simplist terms; it'll net you a bit more range from the missile at the expense of the ability to track a moving target. Getting comfortable with switchology is a bit tough (especially without the TM warthog joystick/throttle). Practice, practice, practice! Your second question is tough to answer without watching you fly. Make sure your flying a stable platform with the nose of the aircraft pointed towards the target you're trying to track, use autopilot as it can help a lot here. Lots of TMS aft short as well! :)

Hehe, I was definitely waiting for Eddie to chime in as well. Seems it may have been in vain though :megalol:

And you're absolutely right. The point track mode uses the same kind of technology that the Maverick missile uses to track an object. Contrast in the image feed from the sensors can be defined by the pod as an "object" in the image and tracked. Probably not too different from the way your smartphone can recognize a persons face when you use the camera

Pay attention to your fuel flow indicators, they display pounds of fuel burned per hour at the current throttle setting. Combine that with an estimated time of flight to a given steerpoint (at a given speed/at a given PPH fuel burn...) from your nav systems and you should be able to do some quick math and figure out when to head home. You can also pay attention to how much gas you used to get to your destination, and make sure you turn back once you reach that number + 1500 pounds (or whatever reserve you think you'll need) I'd assume that the "real" way to do it would be with some fancy chart before a flight but I'm not really in the know on any of that :D I know that some guys around here are though; have you tried searching the forum for bingo fuel calculation?

Awesome!

Same here, It'll get sorted eventually I'm sure :)

Exciting times! ...for you and the testers :D

IIRC it changes dynamically based on your aircrafts position. So if a CCIP solution is available and falls inside the HUD FOV than you're in CCIP mode, if not it'll default to CCRP

It's probably pretty tough to keep updating and improving a sim like this without that issue. Although I've experienced this frustration firsthand many times I'll take the massive growth that the underlying game has made over my old missions any day of the week :)

This was recently posted elsewhere on the forum http://www.liveleak.com/view?i=df7_1393148170 At the 6:22 mark there's a great shot of a plane (I think it's a mustang...) strafing. Pretty smokey!

From the indiegogo campaign statement: "The Project in good state if you can check the project webpage above but I'm a one man team so all of these things made only by me without any supporter. This cause to I need some additional fund to finalize the project. I need a fund to pay the DRM protection, video and sound producing also need to pay a better texture artist than me to improve the airplane presence and outer and inner textures as well." The above statement doesn't line up with the recent posts of other team members. I'm also hoping that the forthcoming explanation doesn't include Beczl's removal from the team. I invested hundreds of dollars into the project and a big reason that I did so was that I trust Beczl who's made wonderful (free) contributions to the community for many years.

1. Apparently that's how the real jet works. That's the explication Wags posted on the subject a while back iirc. 2. It does work (can't confirm in the current build). It should be as simple as setting your A-A TGP as the SPI generator and slaving all sensors to SPI. It definitely worked in the past and is in fact a bit of a workaround to your first problem; as you can see the AIM-9 reticle in the HUD (therefore the A-A TGP line of sight while slaved)

^^^Agreed. From a modding standpoint it won't be an easy fix (otherwise I'd have made an "etched" or black t-80 reticle ages ago). It seems that the coders/artists at ED shouldn't have many issues changing the way it works, although I'm speaking from a point of almost complete ignorance :D Let's hope they get them dialed in eventually!

Red and green can be done easily right now (and I agree, it'd be nice if ED did so with the Abrams reticle and others). I think black would require a slightly different approach to the way the reticle graphics are rendered. I'm not going to do a great job explaining this but I'll try anyway; the reticle graphic is an alpha transparency which means that you can use pretty much any color (iirc) but you can't make it opaque or black. If you try to fill appropriate .tga graphic with black it'll either not render black at all (stay yellow) or be very gray. I can't remember which at this point. Red and green will work though (to some extent).

You don't have to edit any .lua files for that IIRC (did the same edit myself many months ago). You only need to find the missile launch sound and replace it. Hope that helps, if you can't figure it out I'll post up something more detailed when I get back to the home computer

I'm seeing the same thing. Apparently I can still post :)

That can happen for a few reasons. If the target is too far away or if the TGP reaches it's gimbal limits and has to correct (by spinning the sensors back around). In a recent patch the point tracking logic was updated and the latter issue became a more pronounced one.

Thanks for the heads up!

Great work, the night lighting is looking way better.

That might prove to be long term fun for me!:pilotfly: