TacPack for P3D now available

Thanks for checking the FLIR Daube. Must be something specific to my setup then. Everything else works fine.
 
From my side, I've been doing some more tests.
I set P3D to unlimited FPS, and set a 30 FPS limit in the P3D profile using NVidia Inspector.
It works ok, but of course I get blurries more easilly than before. For example, it seems difficult to fly at more than 500 knots at low altitude now. With FPS locked internally, the speed limit is of course much greater.

But still, I can't really complain. In FSX, I could not go past 250 knots without getting blurries everywhere :biggrin-new:

However, in such a situation, my FPS remain sable around 30 FPS (the limit set in the drivers profile), excepted when I switch the FLIR on. Then the FPS drops down around 22-25 with fluctuations.
Also, I had a funny experience when I launched my Harpoons. I created two new wiews on top of my virtual cockpit view to look at the Harpoons flying around (they totally ignored my radar lock...). After a few seconds, this triggered a scenery reload... which went up to 140% ! Now you know why the P3D graphics are better than the FSX ones :bump:

Anyways, I love that bird. Here are two shots: at the parking (a previous flight, trying LGBs) and while shooting my Harpoons. I guess my lock on the radar wasn't locked enough. Both missiles ended up blowing some small AI leisure ships, as if they were launched as "mad dogs"...

daube_image0039.jpg


daube_image0040.jpg
 
I'm using a 760GTX. Not the latest and greatest, but does the job fine. I was a couple of driver releases behind, but tried the latest anyway, with the same result.
 
Found the cause of my FLIR issue, or at least a work around for it. If I have "mipmap VC panels" checked in P3d it works fine, but if I don't I get a CTD. Oddly though, if I turn on the FLIR display, then go into the P3d menu & uncheck the "mipmap vc panels" option, it still works even if I change the DDI to a different page and then back again. Reported it over at VRS anyway.
 
Dave did some testing with the a-10 yesterday and ported that over to Prepar3d and when using the gun I didn't have any smoke effects did you have the same? Tested the f-35, f-14 and the mb335. So far the only thing I can find a problem is the gun on the f-35 which didn't last long enough. Can't wait for the rest of the prepar3d tacpack add ons to come out now. Razbam ' s harrier for one and just flights tornado! Almost can drop fsx completely!
 
I had smoke effects on the A-10 gun, but no sound. Was a very quick test though, & I may have missed something.
VRS have managed to replicate my problem with the FLIR, so that's good. They're looking at it to see if it's a VRS or P3d problem.
 
Did you have a warning about the dsb gauge as I have had that sometimes? Going to see if I can figure out the smoke issue. Hopefully iris get tacpack enabled on the p3d version soon?
 
I think there was a waring about an .ini not being found. Have to go back and revisit that now I've checked the Hunter is working.
 
Just tried the A-10 again. No warnings, & both the smoke and sound effects work for the gun.
 
Figured the issue with the gun smoke. Even though I used the migration tool I didn't have the effect files. Copied from fsx to p3d and now working. I have the same dsd errors when changing aircraft but first loading the aircraft there is no error.
 
You must log in or register to reply here.
Back
Top