radical.ghost

@ rekster Nice Idea, had the same one a couple of days ago. I have already a built - in solution for this: In your Mission - init.sqf / sqs add the following line: "executed = 1;" ( but in the next version (v1.2) I will change that one to be: "IVDS_disabled = 1;" ) That should prevent the AddOn to be activated in that specific Mission. Did only a short test with that and it worked quite well. @ BroK3n That issue you have should be because you probably have the old version (v1.0) of Instant viewdistance installed. Check the first post and grab the 1.1 version from there. That should help.

@ Uziyahu--IDF I'm afraid I don't know exactly what you are thinking of with that. If you want to alter your zoomlevel during a mission I recommend the use of some scopes or a binocular. Also there is a nice AddOn out made by HeinBloed so called GDTModOptics: The GDTModOptics - Addon changes: - Zoom on binocular and laserdesignator. - Clear optics for gunner, commander and all weapons. - No negative zoom on Ironsight weapons. - Smaller aimpoint. - Zoom for gunner and commander (Only commander with weapon). - New KA-50 weapon optics. - Optics for RPG and M136. Calibrated to 300, 400 and 500 meters. Rangefinder calibrated. This is one I like quite much as it gives me some nice and handy features for a lot of COOP - games. GDT Page And BTW: A happy new year to all of you

New Version available for Download, check the first post. @ James2785 Indeed there was something I missed, that AddOn should work properly even after respawn now. ..stupid me.. I could not replicate the problem you had with not beeing able to enter any vehicles. I guess it may have to do with some lag you had in your mission.. And if not, I guess it should be gone by now

@ James2785 No ideas yet, but I'm looking into it. Will see if there is something I missed.. And yes, well recognized the avatar, quite few people out there who know where its taken from @ Opteryx There is currently no limitation on the value you set the viewdistance on and I did not touch that because I couldn't see any problems coming with this. @ Matt Rochelle As I stated before, do not use this in any PVP - type missions.. I know that there are a lot of morons out there trying to get advantage over other players with this AddOn but: 1. There are too many COOP - type missions out there that would need to be updated and re downloaded by every client just for adding a larger viewdistance. 2. Cheaters are able to alter their viewdistance anyhow with little effort and gain their advantage from being able to do so while others are not. So if such an AddOn is available for ALL to download and use, the advantage the cheaters currently have above players will be quite zeroed out because EVERYONE may alter his / her viewdistance to a larger value. My opinion is: This AddOn is meant for the use in COOP - type missions, while it is POSSIBLE, do not use this addon in PVP - type missions. I signed this addon so admins may decide whether or not they allow it on signature verificating servers. So if your server is playing PVP - type missions mostly it would be the better choice to not allow it beeing loaded for the clients, but this decision is up to the admins to make.

Ok, maybe I have found a solution for this problem. As I am not 100% sure if this is the solution and I also may be totally wrong here I think that I should share my experience with this problem anyway due to the possibility that it COULD be the solution: When we had 3 dedicated servers running, we encountered that problem on only one of our servers and we could not figure out what caused it. We tried nearly everything but nothing helped. People with custom faces and custom sounds trying to join this server always got that error message saying: .. invalid custom file ... and were kicked off the server. Since we did not find any solution for this problem, we thought we would have to live with it.. So quite a time ago I also encountered another problem with this server, which I first did not think of beeing connected with the "invalid custom file" - problem, that was that our main administrator did a mistake with assigning the port number to this server. What he did and wanted was something like giving away the port number 2304, but in fact he did a mistake and the server was running on 2316. So our server re - routed all players who tried to join from port 2304 to 2316 ( i could see that by taking a look at the netlog file ). But since quite everything went well with the server (exept that "invalid custom file" - problem) I didn't want to bother our main admin with this minor problem. So how is that connected to the "invalid custom file" - problem? When a player with a custom file joins the dedicated server, the custom file will be saved to a folder that is named like: Tmp2310 (<- this is an example name) or Tmp2304 (<- this is an example name) Where the number following after "Tmp" is the port where your server is running on. So the server gets a problem with storing the custom files in the folder somehow when the port is being re - routed, resulting in the "invalid custom file" - problem. I can't tell much more about this due to the fact I don't know much about the mistake that was done with assigning the ports to the server and how our server admin solved the port assigning prob. But what I can tell is: After our main admin had the server port assigned properly so that the port number showing up in the netlog file is the same number as the one he wants to assign, that "invalid custom file" - problem is gone. Also I can see that now the Tmp - folders on the server are being created with the correct portnumber as name. So if you have that "invalid custom file" - problem, check the netlog of your dedicated server and see on what port it is running (tip: search for the string " Pe(1):srv( " without the quotation marks inside the netlog file) and see if it differs from the port you or your server admin "believe" the server is running on. If it differs, assign it properly so that the port you want to assign shows up in the netlog file and that "invalid custom file" - problem should be history, as I believe. It would be very much appreciated if you would confirm if or if not that is the solution of the "invalid custom file" - problem. P.S.: sorry for my sometimes really poor english as I'm not english speaking by nature..

Hi, when trying to launch ArmA with XAM1.4EN i got the following Error Message: Include File Ca\data\scripts\XAM_FixedWeaponsSettings.hpp not found.