List of bugs in 1.46

[specialswe 0]

BUGS FROM Version 1.46 in Operation Flashpoint

-------------------

Alt. Bug

When Flying the diffrent choppers in the game (Version 1.46) you could

fly how high as you want**. BUG!

**Maximum Alt. 2128

-------------------

Bad Graphic Bug.

I have looked at the UH60 choopers and saw that

the model and textures outside are pretty bad, if

you look at other models (ex. AH-64). So please fix

the model with new "coopit" when you see from outside.

and also fix thoose bad textures!!

- When you see the passanger at the choppers and then

look inside (full crew with passenger) you see that the seat's

isn't the same in as out!

-------------------

Scud Wheel Bug.

I've looked at the scud launcher

when driving it, that the second front

wheels doesn't move when you drive it,

so that isn't really realistic for some missons ect.

Could be greater if all eight wheels moves when driving it!!

-------------------

BUGS REPPORTED BY

Mellis (specialswe)

www.ofp.info

[Mister Frag 0]

You call that a big list of bugs? Those are all cosmetic...

[Lt_Damage 0]

Awesome... make that guy head of OF Developement, it'd be the prettiest ever game that didn't work.

[deady 0]

Revealing units is now a gamble, you see someone, you cant announce them over the radio unless your lucky.

Air To Ground missiles such as AT6's tend to miss horribly, often impacting with the ground PAST the target.

Machine guns have sucked for about 4 patches (bad accuracy, low power).

Laser Designator is close to useless in its current form, AI A10's wont target it by themselves.

Planes (cessna's) start to take damage on the runway if you dont take off quick enough, even though your still going straight with the wheels firm on the ground.

I know theres lots of technical problems people have, but i've only mentioned things here that i can constructively describe.

Just saying "Oh it crashes to desktop a lot" doesnt help anyone, even though it does crash to desktop sometimes

[SpaceAlex 0]

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote (specialswe @ April 02 2002,20:11)</td></tr><tr><td id="QUOTE">Alt. Bug

When Flying the diffrent choppers in the game (Version 1.46) you could

fly how high as you want**. BUG!

**Maximum Alt. 2128<span id='postcolor'>

A bug. You call this a bug. Alt. is not limited anymore in v1.46. Play in cadet mode if u want limited alt.

I prefer unlimited alt. and veteran afcourse.  

[pynaple 0]

just to add to the list.

OH58 seems to be able to take a head on with trees and buildings, not taking any armour damage,not repeatable as then you are a gonner if you try again.(can be a let off but realisim is the key).

Also try a BlackHawk Down drop on a roof and you sink straight in.

Ground textures are flashing on roadways while in flight.

I can live with it but thought some peeps might be having same probs and BIS cannot fix if they don't know of the problem.

[zxc 0]

specialswe's list of bugs is quite funny! But although I think it's not a big matter compared to some other bugs, he's still right concerning graphic bugs: if it can be improved, well that's even better then!

Now more seriously, the lists of bugs specified by Deady and also the "Ground textures are flashing on roadways while in flight" problem from pynaple ARE DEFINITELY the bugs I would LOVE to see corrected by BIS in their next patch.

[ALDEGA 0]

The flashing roads is due to you vidcard/driver. Try using 32bit color and/or w-buffer.

[nra4ever 0]

How about the bug where you get two mouse cursors when you start the game, and have to alt-tab out to the desktop and go back in to fix it?

It may be cosmetic, but it's still really annoying.

[specialswe 0]

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote (nra4ever @ April 03 2002,19:05)</td></tr><tr><td id="QUOTE">How about the bug where you get two mouse cursors when you start the game, and have to alt-tab out to the desktop and go back in to fix it?

It may be cosmetic, but it's still really annoying.<span id='postcolor'>

This "bug" isn't really a bug, its happends when you has some program on, like ICQ opend when you start the game, and if the game is loading from CD, you should not have any windows opened! ICQ should be a minimazied!!

[pynaple 0]

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote (ALDEGA @ April 03 2002,12:54)</td></tr><tr><td id="QUOTE">The flashing roads is due to you vidcard/driver. Try using 32bit color and/or w-buffer.<span id='postcolor'>

Cheers for the suggestion mate ....but

1.45 didn't seem to have this problem(although when I was Infantry noticed grass flash on roadway in one place furthest Western town on Everon). I've uninstalled OFP

caus I had it patched to 1.46 Reinstalled went back to 1.45 just to see if it wasn't my imagination,have always run 32 bit colour,tried the w-buffer.Have the latest nvidia display drivers,even tried going back to previous display drivers,changed refresh rates 70hz and above,changed display 1024*768 to 800*600,

turned off all superflous running programs, icq...etc.

Did all this before I put up my previous post within this thread.

caus I don't like barking up the wrong tree.

specs: p3 800 geforce 2 gts 256 RAM.

Wish it was as easy as you suggested buddy reakon it's a bug for some maybe as it's the same in multiplayer and single.

pynaple out

[ALDEGA 0]

It doesn't have anything to do with any other program running in background. It is a precision error. All objects are placed in either Z or W buffer. Because of insufficient precision, one object is displayed in front of another.

[Tom Gore 0]

I can confirm that reporting spotted enemies does not work unless you're the group leader. Now for more:

- Orders that are given to you AND even one other person do not a) highlight and b) give any markers whatsoever. Orders given to you and you only work fine in both aspects.

- Vehicle commander given orders do not give any markers whatsoever.

- Placement radius in the editor does not work. Objects are placed in the origo regardless of the placement radius. Of course this can be done with a few lines of script but a bug is a bug.

- Hardware T&L still does not work properly with some Radeon cards under Windows XP. Might be a fault in ATI drivers or in OFP.

[ALDEGA 0]

Must be an ATI fault ;-)

It works fine on my nvidia Geforce2

[Intruder 0]

I'm still getting some of the bugs in 1.45, although it clearly says 1.46. And also other bugs, such as the looping medic heal trick amd AI repeating "no target"  

[Diniter 0]

I can't help but think that non of it f-ing matters enough to them to do anything about it. I have come to the conclusion that they are just content with releasing the patches they originally said they would and are stopping. Case in point we got the thread opened (by someone working for BIS) What bugs do you want fixed for the next patch? or something to that effect. People swarmed that thread . There were some good points in it, lots of them actually. So what do we get when the patch comes out (besides broken spirit)? Almost none of what we mentioned was thrown in . Maybe two to three fixes. So I just get discouraged when the posts come in now about fix this and fix that. People pour their minds and hearts into the equivelent of toilet paper to BIS. It doesn't matter does it?

[ALDEGA 0]

Wow, you can't be serious about your statement. BIS has given alot of attention to the fans.

[Diniter 0]

Surprised? I seems to me that with the new Resistance project going they will not be looking to do anything (or little to nothing) for the original at least for this month. The thing that might happen is if something does not mesh well with the addon then the fix for that might flow over into a Flashpoint patch. I could count the (fitting) items mentioned in that thread alone and compare it to the ones fixed and there is no question in my mind they will mostly remain bugs in the game forever. The last patch was pretty lame. And the lack of mentioning another patch is as if they don't have any plans for it. To me that is saying something.

- -edited double negative

[Taku 0]

One bug which should be fixed is the fireplace-bug. We were playing one map where Russians attacks a NATO base in darkness, and there is 2 fireplaces in the base. Defenders DID put the fire off, but attackers still saw the fireplaces in flames... We tested this couople of times, and it doesn't work. If your teammate puts out fire, it's still burning on your monitor...

[ALDEGA 0]

Diniter, the game has been out since june 22 2001. That's over 9 months ago. I can't think of many games that have received support for such a long time. (Yeah we all know Half Life has been getting patches for 3 years. But Valve and Sierra are just milking out that game. They just keep releasing new platinum versions all the time. Would you want OF to be like that?). And remember, this isn't the land of milk and honey. Investing time to research and fix bugs costs time... and MONEY. Money doesn't grow on trees. Don't you agree we've received enough patches and addons (which they didn't even have to do, and they did it for free. Redstorm would ask you $39 for all the addons). BIS are moving on. I'm a very happy owner of this game and I'll be happy when Resistance will be released.

btw, regarding the flashing roads. I disabled w-buffer and the roads don't flash anymore. With the previous nvidia driver, w-buffer worked fine though.

[IceFire 0]

I think it's funny when you are flying a hind low and fast, and you cannot pull up in time to hit a big tree, but you hit the top leafy part and you just bounce off.

It's kind of like a big balloon. You just bounce back.

I hope they never fix that. Lol.

[joltan 0]

Something that really annoys me: the f*cking parser.

When using the addweapon-command in a units init line and you spell the weapon wrong (like "nvgoogles" instead of "nvgoggles") the game crashes to the desktop. You can only hope you saved before that happens, because else you'd have to redo the whole mission...

[Chris Death 0]

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE">When using the addweapon-command in a units init line and you spell the weapon wrong (like "nvgoogles" instead of "nvgoggles") the game crashes to the desktop. You can only hope you saved before that happens, because else you'd have to redo the whole mission...<span id='postcolor'>

Joltan: there's a button called "preview"

This button is there for testing the mission, you made.

During the testing phase, you have a lot of time to check,

if you have done all correctly.

Now the interesting thing: if you find a mistake, you should

correct it. After you corrected all mistakes, the mission is

called: finished

Then you go for the export to sp/mp

At this point is the time where you start playing your mission

(or even upload it anywhere). If you export unfinished missions with even typoo's in some init fields, it wouldn't be

worth playing it (not for you and even not for others)

Edit:

hmm - after reading the post again, i noticed, i got you

wrong. OK but what you talking about, Joltan, is no bug,

more a user fault. I can't call for the programmers, because

i forgot to save data's.

Usually, you should save the mission while editing more

than once. Sometimes pc's goin down, even if you don't try

to play your mission. For example: you are in editor, and the

game freezes after you changed a lot of things. This save

button i'm always using after doing a lot of changes to a mission.

Also you could use the multiplayer editor, because if you click

on preview in the multiplayer editor, the mission will be saved

automatically. You could test your mission even with respawn

in multiplayer editor (makes testing much easier).

[joltan 0]

@DV Chris Death

Oh, so it's a feature, not a bug? The game crashes when I try the preview (to test things out, as you recommended), just because of a typo! That's a bug, even if I did the spelling error. I would expect an error message and the chance to correct the problem without having to restart the game.

About the saving of missions: I save my work regularly, but as it happens sometimes I make some changes and test them and forget to save the mission before I do. Of course, this is an error by me, not the software. Still, it happens - and what leads to desaster is not that I forgot to save, but how easy it is to crash the software.

Never used the MP editor (and haven't seen such a thing - there's a seperate editor for that?), as I only create singleplayer missions.

So here I stand and still claim: the software shouldn't crash because of something as small as a typo in a weapons name.

[Chris Death 0]

The multiplayer editor, you find where you can select maps when you click NEW at multiplayer.

It's the same editor like the singleplayer editor, with the exception, you can invite others to help you testing (for multiplayer missions) and you can have respawn there (very very helpful for testing). You can even create singleplayer missions by using the mp editor. It's up to you, how you design a map, the editor (sp/mp) makes no difference wether

the mission is a sp/mp mission. It's still the job of the creator,

to make a mission for multiplayer.

And a typo is a typo, and you can't expect a program to be able to deal with wrong written words (especially at keywords) a game, where you can change settings in initialisation routines (and there are many changes you can do) can't be able to understand wrong written stuff.

Next time you say, oops i installed a game to the computer of my buddy but i want it on mine - programmer's your fault.

Have you ever tried to create a program in a programmer's language, and put in typo's at keywords?

What will happen? - the program aborts