5.10.01 Vray bitmap renders black squares when using tx file

[ILS]

Converted my jpeg to a tx file using the maketx tool included with vray, but now it shows black patches, this happens only at a certain distance from the object. Moving closer to it, the squares disappear.
Also it renders fine (apart from the black patches) locally, no errors, but gives an error when rendering on the farm

[V-Ray] Error loading texture tile (13, 0) from level 1, file "filepath": 2: error reading file

Narrowing this down the black patches seem to appear when adjusting the Blur value in the Coordinates section of the VrayBitmap. i'm guessing that the new filtering method in vrayBitmap is not compatible with the old one found in standard Bitmap map.
If this is the case then the vray bitmap coverter script should account for that and set the blur value to 1.0 or Chaos should fix the bug if that's what it is.

[ILS]

An update,
there seems to be an issue with the blur value not being set to 1.0.
The above error " Error loading texture tile " seems to be related to the blur value as well.
Setting that value to 1.0 removes the message and the image actually renders.
However in some instances it seems like when setting a vraybitmap in the roughness channel and setting the color space transform to something other than srgb also creates the loading texture tile error.
So the error message is somewhat misleading and this is not a file error but something more internal as to how vray handles the file internally.

[ILS]

ok i give up. Tx file and vraybitmap implementation is clearly half baked and inconsistent.
There is clearly something wrong with filtering of these file types with regards to vraybitmap.
The errors I get have no consistency in when they happen or which texture causes it. Sometimes its the color space transform setting and sometimes its Filter Mult that makes the errors go away, but in a file with hundreds of materials and textures hunting and testing each individual one is not going to happen.
Its too bad because using tx files saves a ton of RAM and renders a lot faster.
Oh well maybe vray 6 will have it.

[^Lele^]

It'd help a lot if you sent support the source texture file, the TX file, and a relevant part of the scene exhibiting the issue.

[ILS]

I filed that as a bug immediately afterwards. I usually don't like griping on the forum but this took me a couple of days, numerous tests and several custom scripts just to narrow down.
It's just really frustrating, for what seems like a bug in basic functionality of the software. Having recently switched to vray5 I've been rather disappointed in seeing Chaos becoming more like Autodesk and using their user base as software testers

More than anything this was meant to let anyone else know who might be encountering this issue, that this might be a potential bug.