Hey all,
Paul Laub sent me the latest Kosta tunes that also now work with P3D. I tried them out tonight. There arent many tunes to do, which I didnt realize. I thought there would be like 20 or 30, but only perhaps 6 were needed. P3D has some settings already that FSX didnt have, which was nice.
I experimented with it, frames set at 30 FPS per Kosta's input. I had them at 36, so no worries there. I went to the worse case scenario, Diamond Point by ORBX, one of my most favorites, which performed so horrible on the new rig, I had written off ORBX airfields. But tonight, it ran very nicely, about 29 FPS.
I did note, at Diamond Point (not at Cushman) that the FPS were at 13 FPS as before with the Kosta tunes, but rebooting and selecting the ORBX 'do not run' on the 5 or so popup warnings (warning, this program isnt tested for P3D, blah blah) for Motion Flow (or what ever those programs are called. EDIT: ObjectFlow is the name of the programs), and my FPS was right up near 30. I was happy.
http://kostasfsworld.wordpress.com/fsx-software-and-hardware-guide/
I was impressed with how you can reroute P3D (or FSX for that matter) to Chip 2 of the quadcore units, keeping it separate from the Windows program traffic. Nice......! Very good to know also about water and reflections, how huge of a hit that is.
Thanks Mr. Kosta!
Paul Laub sent me the latest Kosta tunes that also now work with P3D. I tried them out tonight. There arent many tunes to do, which I didnt realize. I thought there would be like 20 or 30, but only perhaps 6 were needed. P3D has some settings already that FSX didnt have, which was nice.
I experimented with it, frames set at 30 FPS per Kosta's input. I had them at 36, so no worries there. I went to the worse case scenario, Diamond Point by ORBX, one of my most favorites, which performed so horrible on the new rig, I had written off ORBX airfields. But tonight, it ran very nicely, about 29 FPS.
I did note, at Diamond Point (not at Cushman) that the FPS were at 13 FPS as before with the Kosta tunes, but rebooting and selecting the ORBX 'do not run' on the 5 or so popup warnings (warning, this program isnt tested for P3D, blah blah) for Motion Flow (or what ever those programs are called. EDIT: ObjectFlow is the name of the programs), and my FPS was right up near 30. I was happy.
http://kostasfsworld.wordpress.com/fsx-software-and-hardware-guide/
I was impressed with how you can reroute P3D (or FSX for that matter) to Chip 2 of the quadcore units, keeping it separate from the Windows program traffic. Nice......! Very good to know also about water and reflections, how huge of a hit that is.
Thanks Mr. Kosta!