seedhe

@ Deliltmon That texturing on your Land Rover is great!. I consigned some things to the "too hard"/"not enough time basket" and reassured myself with a "I'm just keeping the face count low" without thinking about the overall impact on the finished product having done the bonnet (it added 11 faces) I decided to redo the headlights (300 ish). And although it'll probably be of no consequence in game, it has made all the difference when you are taking a closer look. Looks like you have yours done but if you would like I can send you some links and I have taken stacks of digital photos. Oh and thanks for the feedback. @ Fighter I asked to have the thread moved because the file being mirrored was "pre-beta". I didnt expect for it to be so widely distributed. But the good thing that came out of it was that I was motivated to pull an all nighter on Saturday to get it to Beta stage. Nice Screens BTW. @ Major Fubar I havent come across that (yet). Did you download the original 110.pbo as well as the seh_110.pbo? As you say maybe its a conflict (hopefully...).

The beta version is avaiable as a rar or a zip @ wantingcobra and fighter Thanks for hosting the file, could you update the obsolete file with the above. @Kuba The addon is based on vehicles used by the Australian Army, they are referred to as one tens (110's) or depending on the variant RFSV etc... I'll look into that some more though. @ DKM Jaguar Thanks for the feedback. I havent noticed the flying problem, but the weight is set accurately in Oxygen. I did change damperforce/size in the config because once ingame the suspension was dropping by ~100-150mm (4-6 inches). I will be looking into it. The lights and bonnet issues are partially lazyness and partially trying to keep the vert/face count under 3000 (maybe too low?). I agree that the black has got to go. I like the "3d" effect of the doors but you are right now I look at it again it should be much more subtle. The battery box compartment is modelled in the beta. Again thanks for sharing your thoughts. @ @cero I had made desert textures but to include it (using the only way I knew how) meant adding another 2 p3d's and 2 340k pac's, in the end I decided it wasnt worth the resources. Especially since I had never seen 110s in desert camo. As this is my first addon I'm still learning to walk, once I'm up and running I'll look into the tecniques used by RHS thanks for the heads up. Edit: changed formatting.

Thanks for the clarification. This is probably common knowledge for people familiar with Oxygen, but I couldnt see it clearly at first in my rage at thinking I would have to retexture. Using the face properties dialog (e key) you can edit the path of your textures. You do this texture by texture not face by face, so you only do it once per texture not for every face. Hit ctrl+a to select all the faces then type the current path and name of of the texture you want to edit into the text box at the bottom of the dialog - and press the "filter by" button. You can then edit the path in the text box and click "Ok" and so on for all of the textures. Edit typo

I have had no luck with changing the size of the texture name, hex editing works fine when using the same number of characters but my original path is too short. If anyone has been able to do it could you let us know the method/editor you used.

I have a Radeon 9800 pro 128MB and have no problems with OFP. System- Asus P4c800e P4 2.6c 2x512 ram Radeon 9800pro (Sapphire) Did you uninstall the previous video card drivers before installing the new card?

From an intro to a mission that I never got around to finishing. Small ~ 1.4MB Large ~ 15MB I used FRAPS for the capture and winxp's movie maker for the editing.

(Fixed that last sentence, should make sense now.) </span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE">are you saying the dammaged EH does not work on planes and other vehicles? <span id='postcolor'>Yes that is what I was saying. My original post was not directed at you bn880, just posted to share a script (with the OP) that I came up with when I was playing around with event handlers.

Try a call to this script from your event handler-</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Code Sample </td></tr><tr><td id="CODE">_numberElements = count _this _i = 0 _theText = "" while "_i < _numberElements" do {_theText = _theText + format["_this select %1 = %2\n",_i,_this select _i]; _i= _i + 1} cutText [_theText,"PLAIN"] ;or use ;hint format["%1",_theText] exit<span id='postcolor'> The "dammaged" handler doesnt work on planes or other vehicles.

I see a potentially major problem with maximum flexiblity of appearance/loadouts. Dont get me wrong I like the idea, just playing a bit of devils advocate here. There is a pretty steep learning curve in a multiplayer environment (especially in advanced mode) being able to identify the differences between east and west in the current version of the game. We all have the differences committed to memory by now but if you have a guy 50-100m away running towards your position with a uniform you havent seen before and carrying a weapon you cant identify at that distance, theres gonna be tears

You could set the marker type to "empty". From the comref- </span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE">markerName setMarkerType markerType Operand types:   markerName: String   markerType: String Type of returned value:   Nothing Description:   Set marker type. Type may be any of: "Flag", "Flag1", "Dot", "Destroy", "Start", "End", "Warning", "Join", "Pickup", "Unknown", "Marker", "Arrow", "Empty". Example:   "MarkerOne" setMarkerType "Arrow" <span id='postcolor'> eg. "MarkerOne" setMarkerType "Empty", an empty marker is invisible on the map.

You could get the M2 to target and fire at a barrel, it will continue firing until the damage == 1. So by setting the damage back to zero you can keep it firing. I messed around with something like this a while back but dont recall the exact script you could try something like-</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Code Sample </td></tr><tr><td id="CODE">_m2 = _this select 0 _barrel = _this select 1 _m2 reveal _barrel #Loop ? !alive _m2 : goto "Exit" _m2 doFire _barrel _barrel setdammage 0 ~2 goto "Loop" #Exit deletevehicle _barrel exit <span id='postcolor'> To get the m2 firing in the air setPos the barrel in the loop too otherwise it'll fall out of the sky. The skill of the m2 will effect the rate of fire - high skill  will give you constant fire.

Here is a thread I started in User Missions with a link to an artillery control interface that works in MP. To save a mouse click here is the link to the website. There are plenty of screenshots to help explain what its all about and how to use it.

Try changing the dimensions of your jpg/paa. I think the picture must have sides equal eg. 128x128 or have factor of 2 eg. 128x64.

I have a very very basic demo mission of an artillery control interface here, along with a few screen shots. You direct the fire to the target using a dialog with two sliders to set the direction and distance relative to your own. The demo/test mission has dummy targets that can be played in SP or MP with 3 slots, not very imaginative I know but it gives you the basic idea.

It works in multiplayer, see the readme.txt for details. I wont be adding any way of measuring distances, as it is I think it is a little too user friendly from a realisim point of view. You could do this easily enough with the laser designator and a basic(?) script though I have found with a little practice I will rarely need more than one or two marker rounds to get close enough to the target to be effective. Just keep in mind the grid on the map(when zoomed in) forms squares with 128 metre sides which are ~180 diagonally.

From the Official Command Reference- </span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE">sideChat chatText Operand types: Â Â chatText: String Type of returned value: Â Â Nothing Description: Â Â Type text to side radio channel. Note: this function only types text to the list, it does not broadcast the message. If you want the message to show on all computers, you have to execute it on them. Example: Â Â soldierOne sideChat "Show this text" <span id='postcolor'> The comref is avaiable at www.flashpoint1985.com/doc/comref_102002.zip A comref in the hand is worth two tutorials in the bush.

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE">What about a point and click interface on a map?<span id='postcolor'> I'm pretty sure there are scripts available that allow you to do that. This idea is "loosely" based on a method of controlling fire known as Polar. I found some information about it on a US army web site and went from there. With the Polar method you identify the destination relative to your position then the adjustments are made relative to the initial round. So I didnt use the Polar idea in its entirety just the most convenient part.

It can be used from a vehicle, and the relative position will be your position at the time you make the request. There is a line in the main script to prevent its use in a vehicle but I have commented it out (I didnt get to test it). It could be easily modified so that you give the location relative to the "gun/s" or some other object but this would make it more difficult to use accurately. Id have to take a closer look but it would most likely be a change to one line.

You could set the probability of presence of the groups leader and have - not alive leaders_name in the condition field of a trigger and delete the group in the on activation field.

I have been messing with dialog controlled artillery, It is in the form of a very basic demo mission. You use 2 sliders to give the direction and distance and fire a marker round if you are happy with the settings you fire for effect. The artillery isnt actually fired from the location of the gun but I have attemtped to simulate it. I did find a piece of code on the net, to calculate the trajectory of a baseball allowing for wind resistance and height differences. The calculations are nightmarish and so I took the wimps way out. I'll see if I can dig up the url if anyone is interested and has a stomach for heavy duty math

I am doing much the same thing in a script and what I'm doing is along the lines of- </span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Code Sample </td></tr><tr><td id="CODE">_dist = 2 _dir= (getdir player) _dx = _dist * sin _dir _dy = _dist * cos _dir standort setpos [(getpos player select 0)+_dx,(getpos player select 1)+_dy,0]; _mg="M2StaticMG" createvehicle (getpos standort); _mg setdir (getdir player); exit;<span id='postcolor'>

What is the name of the dir your .oggs are in? Might be a typo, stranger things have happened.

One of the basic issues with multiplayer IMO is the fact that operation flashpoint is not a first person shooter. It is of course much more than that; I guess some kind of fps/sim/rts hybrid. I haven’t played "all" of the FPS games available so I may be missing some setups but in general people fire up their fps of choice select multiplayer and get into the action straight away. If the game type is death-match join and shoot at anything that moves, capture the flag- if you are on red team shoot all the blue guys and grab that flag. Not counting delta force there isn’t a lot of games that do co-op style missions*. So you’ll see endless questions/complaints from people in the lobby wondering/whining about when the next game starts. I am really an rts gamer, lured to the dark side by flashpoint so waiting for a game is nothing new for me but it sure seems to bug some folks. I definitely don’t enjoy the wait but is part of the game, and I'd hate to loose the feel of the game just to allow joining games on-the-fly. So a typical new player who managed to survive the "excruciating boredom" of the lobby is finally in to the pre-game screen. Once they are in the game and its a ctf/team game they don’t know friend from foe and end up tk'ing and get blasted as a 'noob'. Or in a co-op they tk and are a 'dumba$$ noob' or get themselves killed in the first couple of minutes and fly around as a seagull for half an hour. The effect of having only one chance is either you do your best not to get killed and keep your head down or you get a round in the head and watch the action from the sky. Everyone hates getting killed early in the game, but you can learn from your mistake/curse your bad luck and wait for the next round or think 'this game sux' and quit. Don’t get me wrong this has nothing to do with the game as such, it is more a people problem. Most of the "issues" that some of us get upset about are what sets Operation Flashpoint apart. When jumping into mp there is a very steep learning curve, even steeper if the server is in advanced mode. It takes time to be able to recognise the difference between the uniforms and whether that player is carrying an m16/ak74/m60/pk at 100 meters. If people try multiplayer after a few quick single player missions they are probably going to a bit lost to say the least. Busting a newbies chops for making a mistake might make you feel better and maybe that "damned newbie" will learn something but he might take the cd out of the drive and put it back in the box too, scratch one more player for mp games. Then there is the players that want or expect instant action cant understand why there isn’t a server with 40 people sitting there waiting for them to log on before starting. Well in reality not a lot can be done for them and maybe it's for the best anyway.  But seriously for most people with a job/family/real life commitments waiting half an hour to start a game when you only have an hour to play for can feel like an eternity but that is the nature of the game. For me one of the great strengths of the game is Team Work. Team work is probably an alien concept in most deathmatch/free for all style gamers and dieing is only a number in your stats at the end of the game. So folks who previously played these types of games will either adapt or move to greener pastures, again not a lot the flashpoint "community" can do about it. Unfortunately (or fortunately) as history has proven you cant please all of the people all of the time. /me puts rose coloured glasses on The anonymity of the web perhaps sometimes encourages bad behaviour such as team killing, bad language and abuse of admin powers but if the community doesn't tolerate it we may see less of it and more players enjoying more games. /me takes rose coloured glasses off "If you see the flash ... you are already dead" was a great logo for the box but "Like nothing you've played before" is every bit as accurate. * I could be wrong.... It’s happened before and it'll happen again.

I was having the same trouble others have mentioned with createunit and found that the unit that you create to start a group with ( eg. "groupAlpha = group this" in the init field) cannot be a private. I used the "Rank -Captain" and "Unit - Officer". My head hurts too much now after trying to get this working all night to try other combination of ranks but I'm sure others will work.