Uro

Member
  • Content count

    88
  • Joined

  • Last visited

  • Medals

Community Reputation

162 Excellent

2 Followers

About Uro

  • Rank
    Corporal

Profile Information

  • Gender
    Not Telling

Contact Methods

  • Twitter
    @urotsukidoj1
  • Youtube
    channel/UCFMkYjzWz3bMXfjMALoVZUw
  • Twitch.Tv
    urotsukidoj1

Recent Profile Visitors

302 profile views
  1. 16 Months since I asked for Official documentation on the lighting, they also haven't even replied to @PuFu 's request for diffuse/AO baseline bake settings for buildings under the new lighting yet so I wouldn't get your hopes up :)
  2. Hey guys, I keep seeing the same topic of 'How do I get x-cam working with 64bit Arma?' coming up on the Arma 3 discord #terrain_makers channel, so I thought I'd post up this quick guide so it is documented somewhere other than discord and to save me having to repeat myself over and over, anyway here goes... This quick guide assumes you already have X-Cam installed and working with the 32bit version of Arma 3, if you do not then please run through X-Cam's install instructions prior following this guide and validate it is working with the 32bit version of the game first. I will not be offering any support for this since it is simply updated dll's and nothing to do with the inner workings of inidbi nor X-Cam which are both discussed at some length within their own forum threads. Grab the new dll's (iniDB.dll & iniDB_x64.dll) from my github page https://github.com/Uro1/-inidbi (You only need the dll files, the rest of the repository is exactly the same inidbi addon that you should already have installed). Grab make_file_x64.dll from @killzone_kid 's website here - http://killzonekid.com/arma-64-bit-extensions/ Drop the iniDB.dll & iniDB_x64.dll into the Arma3\@inidbi folder. Drop make_file_x64.dll into the \Arma3\ root folder. You may have to 'unblock' the dll files in Windows depending on your systems security setup, to do this right click on each DLL and select 'Properties', go to the 'Security' tab and hit 'Unblock', Click 'Apply', and then 'OK'. Do this for each of the DLL files you have just installed and you shouldn't have any issues with those files in relation to Windows security. In the Arma 3 launcher DISABLE BattleEye. (FYI - You do not need BE running for offline work and there is a chance it will block DLL's used by addons causing you more grief down the road, remember to re-enable BE for online play). Congratulations, You can now launch X-Cam with the 64bit Arma executable as you would with the 32bit version. NB: You may need to grab the Visual Studio 2015 redistributable's (both x86 & x64 versions) from Microsoft's website for the dll files to be compatible with your system, modern versions of Windows should have these installed already but just in-case you run into issues I have linked the download page here - https://www.microsoft.com/en-us/download/details.aspx?id=48145 For those interested I forked the original inidbi repository on GitHub, updated the code-base to VS2015 and compiled both x86 and x64 dll's from the updated code all of which you can find on the GitHub page linked above. I have not updated anything else within the inidbi addon other than creating new DLL files so you can stick with using the default X-Cam install instructions and inidbi setup, then just drop the DLL's into place as described above. As for BattleEye compatibility, I did contact BE via email and requested they white-list the DLL's used by IniDBI & X-Cam and provided the source code to the iniDB DLL's, but they weren't interested and the reply I got wasn't exactly what you would expect from an outfit touting themselves as a professional anti-cheat vendor, so just disable BE to keep your sanity. Hope this helps some of you out on your quest for x64 glory!
  3. Win10 Pro x64 My PC does not randomly lock up like reported above, however TB and Buldozer frequently disconnect from each other resulting in one or the other of the programs crashing and a resulting loss of work. Running TB in compatibility mode does nothing to improve the situation for me and really should be used as a last resort for legacy software that is no longer being updated, afaik the A3 Tools as a whole are still being updated so aren't quite legacy yet. Part of the problem I think Terrain-Builder is having with Windows 10 and specifically the Creators Update that has recently rolled out is that it comes with an updated TCP stack supporting some new features and while TB does not utilize these it will not know how to interpret them either which could be part of the issue I am running into regarding the two applications disconnecting from each other. Prior to this Windows 10 update I could run TB+Buldozer without too much fear of it crashing, although it did, just not nearly as often as it does now. I'm all for TB getting some love from BI since it really hasn't been touched since it's addition to the Arma 3 Tools suite. The GDAL libraries it uses for example are version 1.6x which stem from 2009, that's an 8 year old library now and the current version is 2.2.1 which brings with it a raft of bug fixes and feature improvements. Anyways just adding my 2 cents to this thread, doubt much will happen but you never know.
  4. Please please please redo your low poly on the van and re-bake it from the high poly. There is zero curvature on the wheels, the arches, the doors or the ladders/roof-racks Quite frankly I have seen ripped content with better quality models. All the following screenshots were taken with all video options set to Ultra. The textures on all of the vans are also super low quality/resolution, even if you have to split it across more sections to improve their overall fidelity please do it. For example you can make out individual pixels of a texture easily in-game on these models in all variants, also the rear light clusters and LED strobes on these vans look like they have been copy/pasted into the textures to get around the over-all low quality of the rest of the textures. I don't often crit on BI for their vehicles, while I am no expert modeler either, these vans are seriously sub-par for what is going to be paid content and while considering this has been in development for a year I would have expected far better quality of content and attention to detail, for what is a showpiece of this DLC.
  5. Yeah either your using a different profile OR you had a hard game crash that corrupted your profile data,. this has happened to me before when testing addons and I was sub-25, ever since I have used a different profile for my dev stuff. Luckily the KOTH admins do profile restores for anyone rank 25 or higher so as @R0adki11 says your best bet is to make contact with the KOTH peoples and seek their advice on what to do next.
  6. Disable BattleEye in the launcher, it will be blocking the dll.
  7. Bumping to due to no official response and licenced data packs still being unavailable.
  8. Heya, the links on the licensed data packages page has a bunch of broken download links https://www.bistudio.com/community/licenses/licensed-data-packages
  9. @rksl-rock was working on the QE Class Carrier some time ago. There is a gallery of their models of the HMS Queen Elizabeth on their website - http://www.rkslstudios.info/index.php?/gallery/album/39-hms-queen-elizabeth-cvf/ I don't know if it is still on ongoing project though, you could send him a PM to inquire further.
  10. I never said the language used in some instances on this forum is superior, I said some of the comments I had witnessed on the Steam forums were pretty vile. So please do not misconstrue my comments for your own devices. Anyways irrespective of language used, I am pretty sure the OP and others within this thread would want this thread kept on topic for reasons of clarity to others.
  11. I've been following the revelations regarding the current situation with some intrigue - mostly garnered from various postings on reddit, the arma 3 discord and some of the linked steam workshop/forum pages regarding this. I must say some of the comments on the Steam Workshop are pretty vile, those people should really go and take a good long hard look at themselves. Anyways, following the claims of using BHI Studios content without permission I thought I'd compare the two, so I downloaded SW Opposition and compared it to the previously released BHI Imperial Assault mod and here are the results: I'm pretty sure you can come to the same conclusion I did, that they are most definately using content from BHI Studios Imperial Assault mod. Also note the weapon reticles near the end, they have simply rotated the texture 180 degrees' and are trying to claim it is their own content. If this is what they deem as creating their own content, god help us all.
  12. I've pm'd @TeTeT a link that contains the relevant ILS stuff for setting them up on a terrain, the principles should be the same so here's hoping it's of use :)
  13. There is some truth in that analogy,. however the people who witness that person get pulled end up more aware and less blind to their own actions. Seem's BI mass hit on these offending items has brought some people their eyesight back and maybe, just maybe, it will proliferate down the ranks and make more end users aware of what is (and isn't) uploaded to the workshop by the genuine author(s), as well as what is and isn't ripped/stolen content and what they can expect to happen to those workshop submissions in the future that do contain any offending content. It may have irked a lot of people,. but the workshop and the people who frequently upload offending content have needed a kick in the ass for a long time and I say may it long continue.
  14. I dont think it is closed by a long shot. This issue will continue to be prevalent to Arma and modifying Arma until a decision or method is divulged by BI on the future of modding and monetisation in regards to content creators. Currently it stands as this: Server operators can monetise anything they want provided they have permission(or not) from mod authors and are on BI's "monetised servers list". Content authors only have one option: to release their content freely with no thought towards recompense and have to live with the fact that server operators can profit from their work under the watchful eye of BI. BI have a community of helpful, creative people making endless content for THEIR GAME for FREE and they don't even bat an eyelid when a highly contentious topic arises(this one) about "monetisation" and how out of balance it is in Arma. Modifying Arma at the end of the day sells hundreds of thousands more copies of the game on BI's behalf than would happen with just the base game. The same can be said for thier previous title, Arma 2. Sure it had a large milsim following, but without the well known and highly publicised modification DayZMod, would BI have sold half as many copies of that game in its' later life as it did? So BI wins and so do server operators, content authors lose, every time. Don't get me wrong, I enjoy being creative, but something severely stinks with the current setup and unless something is done to rectify it this community will continue to bleed content authors until there is nothing left due to the way they are unfairly penalised, whether intended or not.