MTrenda

not sure of the issue, but have to ask do you have other windows open at the time. when I alt tab out of DCS in windowed mode I have at least one active application running. Teampspeak, EVGA software, something small so no resources are taken. TeamSpeak needs to be active window and not minimized to the icon tray. this should allow you to get the Alt tab selection window and select the application you are looking for. probably not the issue but thought I would put it out there. thanks Falcon

Fired two sidearms at an SA-8 and SA-6, with direct hits sidearms exploded in a fireball but. no damage at all. I then shot a maverick at each and they exploded on impact and destroyed the targets is this for everyone or just me? thanks Falcon

I can confirm this same behavior with a group HumVee tow unit. The Jtac stops responding after the 0=line. I have gotten pasted it a couple of times by check out and then recommitting but it is hit and miss and frustrating. Thanks Falcon

oh woops sorry, will have to switch to the open beta. thanks falcon 76

yes I can hear the refueling sound after the disconnect with the tanker. it is very notable in the f2 view thanks Falcon 76

yes I had I t happen last night. I am running 1.5.5.60565 will run some more tests. thanks Falcon 76

Issue - after AAR Refueling in the A-10 the refueling sound continues to Replicate - do a AAR refuel and then disconnect and hit the F2 view, I you land and turn off the engine you can hear it as plain as day. I have not tested refueling on the ground yet to see if the issue is there also. I will try today. the sound of the refueling is awesome and love that you added it. Thanks Falcon 76

thanks for the response 76th falcon

TwoBells, I agree the tooltips are very problematic for VR users. One the box does not need to be 20 lines long, if the tools tips is that big someone should reading from the manual 2,3 lines is more appropriate, five max. Two the transparency of the box could be increased so only the text is shown, this should reduce the amount of interference of other gauges. the problem with the current transparency is that at night with NV on the boxes become very difficult to find the correct switch in the cockpit. we also can not rely on mission designers to set this setting to tooltips on but not enforced and even if they did the functionality is problematic at best. so two suggestions for the devs: 1 - make the box dynamic to the amount of text 2 - turn the transparency up to almost full thanks Falcon 76th

It appears in the last update I am unable to get helicopters to land on any non level terrain. if the terrain is slightly banked the unit will hover and not land. I have attached a mission to show the behavior. previous to this the chinooks would land just fine in all three of these areas. thanks 76th Falcon Helicoptertest.miz

Entropysg, I would suspect the group is not spawned with AI on. not able to test right at this minute but try spawning a set of mortar troops instead of the crate and see if they fire. I suspect they will, if I get a chance I will try to follow the code to see how unpacked unit are spawned and see if the ai is on of off. thanks Falcon76

Maddog, I am not the expert in this script but looking at the code, 10 troops is the default amount of troops to be picked up defined by "ctld.numberOfTroops = 10 -- default number of troops to load on a transport heli or C-130" so if no troops are in the area of the pickup zone then ten troops will be put in the transport. I have not looked at your mission yet but I think the function you want to control the number of troops and not use the default is ctld.spawnGroupAtTrigger("GroupSide", Number, "TriggerName", Radius). this also sets it as extractable. secondly since the function to load and unload troops is the same ounce troops are on a transport you are not able to pick more troops until the one group is dropped off. this would require the original troop group to be removed from the pickedup table, storing that information in a variable getting the new troop information, type, number and adding those type to a new group. this would be a collection of both groups and then the second pickup group be deleted. this would have to be a separate routine from the pickup and drop off routines. This could be done but if would be an enhancement, I think. I like the idea and maybe Cribob can look into it. I will see if I can't look at what you have later tonight right now have to tend to the family. thanks Falcon76

Ciribob, I wanted to know a couple of items: 1. is there a way to call the listRadioBeacons ADHOC. I want to add it as a triggered action for a unit called Atis when a Heli tunes to channel 117.00 and receives the list of beacons 2. the cratesInZone does not seem to count the sling load Items, is there a way to get that to work? it works fine if you are not sling loading but you are using a unit when loading on the heli, sling loading you are using a static object (cargo1) so I am not sure it is in the list of item to count. 3. the countdroppedUnitsInZone seems to return double the number of unit s at the fob. if I drop 8 the count comes back as 16. I am trying to redo the Airmobile Operations - frontline mission by angle so I will attach the mission with it set not to sling load there has been no modifications to your CTLD. thanks in advance for taking a look at this one. Falcon76 UH-1H Airmobile M04 - Frontline v1.08.miz

Skatezilla, perfect exactly what I wanted. thanks Falcon 76th

I was hoping for a way to launch DCS without the oculus rift engaged since when the oculus rift is engaged the screen resolution is all messed up, thin and vertical. I would like to be able to work on missions without the oculus and right now I have to turn off the oculus in the options and then restart. it would be nice to be able to create a shortcut with a parameter to turn off oculus so the screen resolution is correct. then the regular launch icon would launch with oculus rift. let me know if you need further details or if it already exists and I just missed it. thanks Falcon 76th

confirmed that movement of the track IR is not in relation to the previous version. very limited movement and recenters in different places in the cockpit. sometimes to high can't see reticle in p51, other time just right , and then again sometimes to low. this all depends on what head movement proceeded the centering. thanks Falcon

Dragon, awesome project, looking forward to its release. thanks Falcon

SAGEOT, The lastest Version 2.4.1 should be independent of all other mods. Please remove any previous versions and install 2.4.1. if it still is not working I will need a copy of the mod that is not working. Also a description of the issue. thanks 76th Falcon

Skulleader, nice work, your cockpit is awesome. thanks Falcon76th

hokum52, I took a look at the download and a few items seem to be amiss here: One: The database cars file references the Ranger pack Chassis and they are not in the download this is an issue since the conflict of the two mods will cause one of them not to work. Resolution copy the contents of the chassis file and paste in the Vehicles that needs these chassis files. (see the screen shot). This is only a problem because the same code will need to put in all the vehicle that reference the chassis, the plus you can get rid o the DB_units_cars requirement and the chassis folder. No more conflicts and no more dependencies on ED changing something. More then likely I will make this change on the next ranger pack update. Two: it appears there was a secondary declaration of MAZ543M.lua not a problematic other then you are overwriting the original which is ok if intentional but if not then it is not required. Three: the two units in question "ATGM BRDM-2 9P148" and "ARV BRDM-1" seem to have something wrong with the liveries folder. Not sure what or why at this time but both of these are showing as shadows and this is usually because it is unable to apply the correct texture for some reason. will need more research to find a resolution for this issue. recommendation: add the chassis information into the vehicle lua's that are affected. Remove the chassis folder and the DB_units_cars requirements for now. thanks Falcon76th

Hokum52, do you have a place for me to download the mod? I can then take a look at the file structure and see what is missing? thanks Falcon76th

Hokum52, Ok, what I found when we had to do the 2.3 update: Each vehicle has a chassi file associated with it, which defines characteristics like weight, speed, gears, max slope, acceleration etc. If the installed mod refers to a chassi lua that is not in the DB_units_Cars.lua then the game will crash. Most mods just use the predefined chassis but having a Toyota truck use t-72 frame would not be a very enjoyable drive. With this information I would say that one of the Mods you have is not getting removed when you do the update and it is referring to a chassis lua that is not defined in the DB_units_cars.lua To resolve the issue I would do the following as painful as it may be. Remove all mods that are not ED (including manually installed mods). Review the DCS world\mods folder to makes sure only ED MODS are listed. For example: ( not going to list them all) under aircraft: A-10c, BF-109k-4, etc. (these are the one's you purchased) under Tech: combinedarms (if you purchased it) terrains CaucasusBase Once this is done I would run a repair using this Article: http://forums.eagle.ru/showthread.php?t=114030 Validate that DCS is functioning as expected. if not we will need to look somewhere else but this should work if the only thing you have installed is ED approved installs. Now take each mod and install it one by one and each time you add a mod launch DCS. at some point DCS will fail to load and at that point we will find the offending Mod. Keep in mind that you should not install the Ranger Pack in this process as it will replace the list of available chassis and fix the issue. Once we find the offending mod we can look at the Lua and determine the chassis type or other config issue. Good luck, and the more systematic you are the more successful the outcome. Thanks, Falcon76th

Hokum52, I always remove my mods before any updates and then re-apply them after the update. We are having to modify an ED File because we are defining some new Chassis types and if the mod is applied and an update or repair is done then those chassis are not defined and the game crashes. This occurred recently before the 2.3 update. Ranger 2.3 update was to fix this and we have not found a way to use Custom chassis without defining them. So if you are saying that when you update your game you have to re apply the mods this would be a true statement and will continue until we find another way to define custom Chassis. thanks Falcon76th

.

hokum52, Can you tell me: what version of ranger pack are you using (2.3,2.4) What version of DCS (1.5,1.5 beta,2.0) any other mods installed besides this one, if so which ones? how are you installing it (jsme, direct exctract, manual copying the files) thanks Falcon76th