May 21, 201412 yr Hi, I've had a quick look through the source code that ships with tileproxy, and it looks like it wouldn't be too difficult to change things so that it also works with P3D (rather than hacking P3D to look like FSX). Has anyone tried this? My only concern is whether the driver identifies FSX.exe, but a quick scan through the sys file does not reveal an fsx.exe string anywhere. Bryn. Streaming at twitch.tv/brynmwr
July 27, 201411 yr Hi, I've had a quick look through the source code that ships with tileproxy, and it looks like it wouldn't be too difficult to change things so that it also works with P3D (rather than hacking P3D to look like FSX). Has anyone tried this? My only concern is whether the driver identifies FSX.exe, but a quick scan through the sys file does not reveal an fsx.exe string anywhere. Bryn. I wish I had this knowledge in order to help you do it, because this is the right way, modifying Tileproxy, not P3D. Anybody help us ?
August 12, 201411 yr I tried but without success, Visual Studio threw tons of errors at me so I didn't manage to compile anything...
July 30, 201510 yr I took a shot at this recently, without much luck. Altering TileProxy wasn't too hard, and I got it to compile (always a pain on Windows), but it didn't work. P3D wouldn't even try to actually read the .flat files. Not sure why.
July 31, 201510 yr Author Perhaps the tileproxy.sys driver is the problem, then? I'm not really sure what that driver actually does... Streaming at twitch.tv/brynmwr
July 31, 201510 yr So far as I can tell, it's a Windows filter driver which intercepts file requests matching a certain pattern and forwards them to TileProxy (or, any program which connects to it). It doesn't seem to care what program sends the requests, and you can see this by looking at the files in Windows Explorer or something when it's running: TileProxy will spit out a bunch of messages about unexpected requests or some such. So I doubt it's the problem here. My best bet at the moment is something with the static .bgl files that P3D doesn't like. It could be something with them being in an old FS2004 format which P3D no longer supports, or something. I'm not really sure. It definitely reads those, they show up in P3D's "open files" list, it just never seems to actually do anything with them, including the LOD8 ones which should replace the terrain even without TileProxy running.
Create an account or sign in to comment