- User Since
- Mar 27 2015, 5:27 PM (315 w, 2 d)
Jul 2 2020
I've had this issue for quite some time, happens every time with me as in the first 'Not Working' video, at first i thought it was a router port conflict with other computers on my network, but even with those powered down and disconnected the issue is still there.
Apr 16 2020
I just checked latest game update v:1.98.146303
Mar 27 2020
I dont have dev-branch installed atm, from @Groove_C 's video it looks fixed, would need a final confirmation after RC and subsequent Main Branch update to ensure it is within the next Main Branch game update.
Mar 2 2020
Jan 2 2020
Dec 27 2019
Dec 18 2019
Dec 3 2019
Aug 6 2019
I was helping Flix on Discord, we tried the usual culprits like ensuring drivers are up to date, verifying game integrity, etc.
Jul 14 2019
Can confirm this issue from the repro steps, would be good if this is fixed as it's an animation issue and may factor into more than just house simulation type.
Jun 26 2019
Issue seems to be fixed in Dev Branch rev. 184.108.40.2068 from today's date (26/06/2019).
Jun 13 2019
This issue still exists on Dev Branch rev. 1.95.145757 and Arma 3 RC 194 rev. 1.94.145759 from today's date (13/06/2019).
Jun 7 2019
May 10 2019
May 4 2019
Any updates on this issue from Bohemia?
This has been on the issue tracker for almost a year and not even acknowledged by BI for something that would be a relatively easy fix and require minimal work on their end.
Jul 12 2018
May 2 2018
You are unfortunately missing the point.
Changing operating system to get around an issue does not actually fix the issue.
Apr 27 2018
@Wulf any updates on this issue? It has been in the wild for some 6 months now.
Dec 12 2017
Dec 3 2017
Nov 20 2017
Aug 4 2017
No takers on this issue from BI yet? Ticket has been active for >7 months with no actions.
Feb 3 2017
Thanks for the update @Alwin
Jan 31 2017
Jan 27 2017
Aug 16 2016
Any more news on this issue? it is still present.
Jun 2 2016
That PixelShaderID is designed for using 5 surfaces + normal mask.
May 31 2016
Already stated ours is completely custom config, i.e. everything IS custom.
Unfortunately that doesnt help us and many others out.
May 23 2016
Any updates on this? Issue should still be marked open, since it still exists. See https://forums.bistudio.com/topic/190972-ingame-map-satellite-image-bottom-is-not-generating/
May 21 2016
May 20 2016
May 10 2016
Related to and enhancement of http://feedback.arma3.com/view.php?id=27392
yes, open/close named selection in memory lod works while on ladder
Update: example model passed onto razazel@BI
yeah sure, do you have an email address or something to send them to? I rather not publish them on an open feedback tracker :)
alternatively PM me on Arma3 discord, user @Uro, and I'll happily give you a dropbox link to a zip file with the model in the screenshot
Assets/Objects with class=House in GeoLOD and incorrect config.cpp entry I.E. not defined as a land_ class can cause Binarize to crash which results in Terrain PBO created without WRP inside.
Grabbed from PboPro window, using latest mikero pro tools(09/11/2015) and binarize(dev branch, 220.127.116.11):
Binarise crashed with error status -1073741819.
Depending on the number of goats you sacrificed,
this may, or may not matter.
Any building that has animation - ladders / doors / ruins+destruction class / hitpoints / etc, requires class=House in GeoLOD and class Land_ config.cpp entry, else Binarize crashes out-putting the error above ^.
Hope this aids you in adding error reporting to Binarize &/or some sort of included document that references these errors + how-to fix would be useful instead of searching for the illustious needle in haystack ;)
We backtracked via our git and found the issue manually and fixed it, so unfortunately we cannot repro this using the latest binarize as we fixed it manually via reverting commits.
But better binarize error logging would have saved us a weeks worth of sifting through data and a possible terrain revert to last working full build. Which would mean 1 months of collaborative work could have been wiped, and we would have had to manually check/re-check everything added from that point to ensure the error wasnt replicated elsewhere.
If it happens again I will report any updates to this issue, along with relevant data and create a clone of our repo at that point for testing binarize.
is related to this issue.
Attached screenshots, binarize.RPT, bidmp & mdmp from binarize.exe
Any progress on this? Would be a cool feature for asset creators!
I had the same issue on Saturday - 11/07/2015 - with the same error messages.
It ran perfectly 2 days prior to this - no software updates of any kind were added to my system other than Microsoft Security Essentials Definition updates.
I updated my Nvidia drivers to 353.30 from an outdated version and it seems to have fixed it for me, no crashes since.
System Specs for comparison:
Intel i7 4770K @ 4.5Ghz
16GB DDR3 RAM
EVGA Nvidia GTX 650 Ti Boost SC 2GB
Windows 7 Ultimate.
hey tom, I thought my terrain's map was fixed, but alas it isn't.
I was encountering the tartan when zooming in before, and now only when zooming fully OUT I still get that dreaded tartan :|
If you need anymore info from me, or if there is anything I can do to assist throw me a PM on BI Forums - Username: Uro1
Any updates / progess on this?
It's been 4 months since last ticket update by BI....
Thank you Neo & Miro for the time you guys have diverted from your own work into these issues :)
Without people who have your level of techical expertise looking into and tracking down issues like these - the arma community and especially the terrain building part of it would be at a loss :)
Richie made a post on the BI forums with his mapframe settings - which would be "quicker" to generate source files for.
See his post here - http://forums.bistudio.com/showthread.php?190615-Error-Satelite-overlap-issues
And a screenshot of his mapframe settings - http://i.imgur.com/LzYbFPp.png
Icebreakr and Jakerod are also generating coming across this "tartan" bug with varying mapframe settings they are using, I will try to get them to post up thier mapframe settings also :)
From chatting to BISIM guys - they have never seen/heard of this error while using VBS and told me that VBS works with pretty much any setting they throw at it.
I'm thinking some bugs may have crept into TB when it splintered from VBS affecting the mapframe computations.
There is also another similar bug report already on the tracker here which has more repro data -