Skip_Moniker

How do I make my MP mission players respawn? I have set up 2 squads and made each unit in both squads 'playable'. But when the player dies he becomes a seagull even when the rest of the squad remains alive. Does each one have to be inserted as a group? Thank you...

If I understand your question, it depends on the config. Â If you have instant or base respawns (respawn=2 or 3) in your description.ext then you respawn as yourself. Â If you have a group or side respawn (4 or 5) then I think you respawn through all your playable units. Â Each playable AI unit has a unique name, and maybe a different rank & loadout. I'll try it again but I think that's the way it works.

I had similar graphics degradation. I tried many different settings and drivers. Two things finally fixed it for me; I disabled (unchecked) write combining in the advanced display properties > troubleshooting. Then, in the nVidia control panel I set up program specific settings for ArmA and changed the 'Force mipmaps' to 'None'. That completely cured it. Don't know why it worked because I had both set that way before, but just not at the same time. No other settings or combinations of settings made any difference...for me. AMD 64 Athlon 4000+ Biostar 6100 micro ATX Corsair 2GB BFG 7800GTX Audigy 4 WinXP

I heard of one other solution to this, but I haven't tried it. In your system audio volume sliders, go to the 'recording' section and mute everything except MIC. If you don't have mute just move the sliders all the way down, except for MIC.

Ventrilo was so bad for me it was unusable in ArmA. Tried many different settings -- nothing helped. Then I started running it on a 2nd PC (not on the game PC). That's the only thing that worked for me.

It's my own 'beta' mp mission I'm working on. Now I find that it changes slightly if the AI squadmates are configured as 'playable' or 'nonplayable'. If they're nonplayable then I only respawn through my squad. If 2 squads all are playable then I respawn through both squads, in other words, the entire side. I don't know if this is affected by players joining the mission. I have only tested it alone; i.e., no other players in the mission.

Not sure what u mean. I'm using side respawn now. In my first & only mission so far I have 2 squads on one side. When I die and respawn through all of my squad 1, then I start respawning in squad 2. As long as there are AI alive on my side, I continue to respawn. I thought that's what a side respawn is? I figured a group respawn would limit your respawns to your squad only. I haven't tried that type.

Can't you just download it again? I'd try that first. Your graphics problem may be a separate issue, though.

Thank you, I am new to this site & did not realize there was a search feature. Â So I did find out basically how to do it, but the finer details left out had me confused all day. Â For the benefit of other 'noobs', here's how I finally got it to work: Â 1. Create a mission using the ArmA Editor. Â You may optionally use the MP Editor too, but it takes longer to open & saves go to a different folder. Â 2. Save your new mission as a 'User Mission' and name it whatever you like. Â Exit the game back to desktop. Â 3. Open a blank Notepad & insert 2 lines: respawn=[RespawnType]; respawndelay=[DelayInSeconds]; Â Substitute your type of respawn and respawn time delay (in seconds) Â Types are: 0 or "NONE" = No Respawn 1 or "BIRD" Â = Respawn as a seagull 2 or "INSTANT" = Respawn just where you died. 3 or "BASE" = Respawn at a basemarker 4 or "GROUP" = respawn in your groups ai. 5 or "SIDE" = respawn in your sides ai. For example: Â respawn=3; respawndelay=4; 4. Close & name this new file 'Description.ext' & save as 'All file types' to the folder '/.../My Documents/ArmA/missions/[mission name]'. Â There should be a .sqm file there of the name you gave the mission. Â Note that if it gets saved as 'Description.ext.txt' rename it and remove the '.txt'. Â It then becomes a Windows unknown file type. Â 5. Start ArmA and return to the Editor. Â Load the mission you saved in step #2 6. Place a marker at the location you want players to respawn. Â You will have to name the marker one of the following: Â respawn_west respawn_east respawn_guerrila respawn_civilian For the people that didn't play ofp: West = bluefor East = opfor guerrilla = Independent civilian = civilian The rest of the marker details are up to you. Â If you make the marker a bigger size, like 100 by 100, you will respawn somewhere inside that area. Â You can also make multiple markers for the same side, nameing them respawn_east1, respawn_east2, etc. Â This will make a random respawn 7. Save the mission again but remember that the respawn doesn't work in preview mode. You have to now export it to multiplayer to see the effects. Â If exporting to SP, remember that a SP mission must have one unit designated as "Player", whereas a MP mission only needs one "Playable" unit. Â 8. Exit the editor and open the SP or MP mode (whichever you exported it to) and play the mission to test it Thanks to the dozen or so users I plagerized to complete this step by step.

How do I make my MP mission players respawn? I have set up 2 squads and made each unit in both squads 'playable'. But when the player dies he becomes a seagull even when the rest of the squad remains alive. Does each one have to be inserted as a group? Thank you...

That didn't work either. Neither did DriverCleanPro. Then, I set the HDRPrecision back to 8 in the ArmA.cfg file. Played about an hour with no problems (except that crazy blinding effect is back). We'll see... [There's at least 2 threads going now that appear to be the same problem]

V8, it appears you're having troubleshooting (hehe).

Well, the graphics problem just happened again despite the cooling efforts. Next, I'll try the VSync setting on app controlled in the CP. Currently I have it set on 'force off'.

Adding an Air Attack group I know they don't line up where you put them. Not sure about other units. Cobra's get scattered around the area while the editor shows them together in a neat row. One of mine was dropped inside a hangar. I managed to fly it out through the large door anyway. Screwy thing is, when I wanted to put one inside a hangar I couldn't. It's all by chance seemingly.

Yes, & I'll add a another part to my story. About the same time as the overheating problem my card started to whine; softly at first but then very loud. I took it out and found that some clear plastic wrapping, like the stuff you peel off from new hardware panels, was caught in the fan blades. I didn't mention it before because I thought the overheating came first & caused this stuff to bubble up inside the fans housing, then the fan blades grabbed it. God only knows why BFG puts this stuff inside the fan housing, but it took me an hour pull it all out with a tweezer. It looks like it's supposed to be an insulation barrier or something because it sits between the faceplate and heatsink. Normally the screws holding the faceplate on keeps this plastic film taught. But in mine, I think excessive heat caused it to separate from the underside of the faceplate and the fan just pulled it in. Again, I think this was secondary to the heat yet there was no significant dust in mine. I should also mention that this was a replacement card (lifetime warrranty) because my first one died after about a year. I'm thinkin' now 'twas heat that probably killed it.

I had a Logitech Extreme a couple years ago that did the same thing (obvoiusly in other games). It was only a couple months old when that problem started. I found a tech paper that said to disassemble it and lubricate the reostats, or some such thing. I threw it out with the other garbage and bought a Saitek. Needless to say, me and Logitech have parted company.

I had the same problem until I realized that 'Open fire' & 'Fire' are not the same. Make sure the command you're giving them is 'Fire'.

Same thing here; severe graphics degradation after about 20min of play then a quick CTD. Â Not overclocked at all yet vid card was very hot - too hot to touch. Â I put a temp probe on the cards heat sink & it and it read 75C. Â Removed case panel and blew more air from a small (6in.) electric fan. Â Temp dropped to 69C and problem did not recur, at least not yet. Â Without game running temp fell to 45C. Â CPU heatsink probe reads about 31C and doesn't change much. Â My room temp is 21C. [card is a BFG 7800 GTX/256mb]

Well, it appears that my shut down issue was solved by a new power supply. Â Not a better one, just a replacement of one with the exact same specs and size. Â However, since it was rather random before I can't be 100% sure over such a short time of use as this. Â The key was it started happening in another game, X3 Reunion, whereas before it was only during ArmA. Â It was then I became reasonably sure it was a hardware issue for me. Â I'm not a techie, but I figure there must have been some kind of voltage shortfall, probably to the PCIE bus, such that when a certain demand came, and supply was inadeqate, it would simply shut off. Â Then, over time, it got worse and began affecting other applications as well. Â I realize this won't help you guys with rebooting problems, but others looking for answers here may find their problem is similar to mine. Â It seems to me however, if you provide the right envoronment, this game obviously works (doh). Â Creating that environment can be a problem considering the huge variety of systems we're trying to use it on. Â Then, when you throw in software conflicts or hardware malfunctions like mine it can become very hard to sort it all out; maybe impossible. Â I wish I could help you more than that... AMD 64 Athlon 4000+, Biostar 6100 microATX, Aspire X-Qpack (420W PSU), Corsair DDR 2GB, Maxtor 120GB IDE, BFG 7800 GTX PCIE, SB Audigy 4, Windows XP Pro

I have the same problem with the US demo. Â My PC randomly shuts off during gameplay. Â It only happens with the ArmA US demo, the EU demo did not do that. Â Furthermore, it's not consistant. Â Sometimes I can run it for hours and it doesn't shut off; then again sometimes it shuts off a moment after I spawn. Â I play some other 3D games (COD2, HL2, Flatout2, Pacfic Fighters, X3, TigerWoods '07) and have had no problems there. Â Still my feeling has been that it is power supply. Â I figure there's some extra demands for power in ArmA and my specs are not meeting it. Â I have a CPU temp probe and it's not overheating. Â I never overclock, nor underclock, and I have all the updates I can get. Â I don't use antivirus nor anti spyware. Â My system is AMD 64 4000+, Biostar microATX 6100 w/nVidia nForce chipset, BFG7800 GTX, & SoundBlaster Audigy 4. Â I have one of those Aspire X-Qpack cases with a non-standard PSU. Â It's only 420W and can't be upgraded. Â A standard PSU won't fit [either the PSU or the optical drive would have to be mounted outside the case!]. Â So, I guess if the retail version won't run either then ArmA will be shelved until my next system. Â Maybe by then all the other bugs will be worked out too.