zbysiek

@BIGNEWY Please remove the fixed tag, as the issue is not fixed and appears worse than before. I had to drop my mouse polling rate to 125Hz for the stuttering to stop completely.

i guess i'm gonna go f myself

I meant that the GBU-12 get their appropriate laser codes loaded into the DSMS instead of defaulting to 1688, I see no reason why the LJDAMs shouldn't get the same treatment and allow us to change the initial laser code in the rearm menu.

I meant the DTC that's already built into the A-10C, eg. loading DSMS data. The GBU-12s get their laser code loaded in that way automatically, if you didn't change your TGP code, you'll get a "LASER CODE" warning when selecting them and with autolase on.

https://www.digitalcombatsimulator.com/en/files/3344305/ Lines 268 - 273, it's a 5 minute fix.

GBU-54s need to be re-programed manually in the INV page after loading the data from the DTC. I think we should be able to select the laser codes from the rearm menu, and they should transfer alongside other DTC data to the aircraft, just like GBU-12s and AKPWS do. Feel free to prove me wrong and tell me that i'm an utter idiot. GBU-54s: GBU-12s:

Will the map be available as a free trial in the near future? I would like to test out the performance before buying it.

Looks like you deleted too much stuff when copy pasting, the lines don't match the original script.

For people that bought them, how are they holding up? I currently see them for 180$ with tax on AliExpress.

Only for now, or only only? Does JSC have the authority to pull the products from other markets?

the workaround is to fly from the CPG seat

The project is on backburner due to the recent changes that ED made regarding texture streaming, as of now i don't recommend using any 3rd party mods, DCS is just too unstable on it's own right now. I'm gonna return to in in a couple months when they fix the stability for everyone.

Can't install: 3341805 - 404 3341958 - 7z error 3341956 - 7z error

Thanks for the suggestions! It's definitely doable with the already existing filters, just gonna need to run the script a couple of times. I'll try it out when I wake up.

For folks that fly a bunch of things and not just one airframe, it's very cleary that a lot of modules suffer from inconsistency in texture size. Apache might need a medium setting, while a Huey definietly needs Ultra. Other user already suggested a texture setting per module, but i think choosing the right texture size based on.. it's size might be a better solution to the problems of some modules having too high textures on the "High" setting. The problem is very pronounced with the Medium setting looking more like Low than Medium, looks like it's 1024px, some users even manually resize the textures of new Modules like the Apache, A-10C II or the CH-47F down to 2048px to get better performance while still maintaining better quality than the "Medium" setting. Can we get more texture quality options? And instead of them being a factor of the original texture resolution, make it so it picks it depening on the actual texture size (or the highest possible if that texture size doesn't exist). e.g: Potato - 128px Ultra Low - 256px Low - 512px Medium - 1024px High - 2048px Ultra - 4096px