Devilchaser

My guess is that an object is only allowed one animation. I messed around with that gate too, great example. Hopefully we'll discover exactly how these animations work. Wouldn't it be nice if BIS put up a post about how their new functions that came with resistance can be used?

My guess is that an object is only allowed one animation. I messed around with that gate too, great example. Hopefully we'll discover exactly how these animations work. Wouldn't it be nice if BIS put up a post about how their new functions that came with resistance can be used?

One thing that makes using O2light really tough is the lack of a texture previewer for your texture directories. The preview you get is only for textures that are already in your model. Considering that the amount of textures available from the commercial Opflash and Resistance is in the hundreds, we should always check those first before creating custom textures for our model. The problem is, you have to load each one individually to see what it looks like. We could really use a small utility that lets us browse all the textures within a resource folder so we can choose what textures we want to use. Anyone know of such a utility? Or perhaps a website that has posted all the texture pics? If none exist, as a community we should make one.

One thing that makes using O2light really tough is the lack of a texture previewer for your texture directories. The preview you get is only for textures that are already in your model. Considering that the amount of textures available from the commercial Opflash and Resistance is in the hundreds, we should always check those first before creating custom textures for our model. The problem is, you have to load each one individually to see what it looks like. We could really use a small utility that lets us browse all the textures within a resource folder so we can choose what textures we want to use. Anyone know of such a utility? Or perhaps a website that has posted all the texture pics? If none exist, as a community we should make one.

always use tab or spacing to organize your class structure. It will help you tremendously. Example: class cfgweapons { class default {}; class mgun : default {}; class myweapon : mgun { displayname = "my weapon"; }; }; //=============== see how much easier that is to read? Try that and I think you'll see where that error is.

always use tab or spacing to organize your class structure. It will help you tremendously. Example: class cfgweapons { class default {}; class mgun : default {}; class myweapon : mgun { displayname = "my weapon"; }; }; //=============== see how much easier that is to read? Try that and I think you'll see where that error is.

Of all the things I've done in O2, getting those normals to face appropriate directions is the toughest. There seems to be very few options for them, and it's very important for many things. Anyone have any techniques they would like to share with us about adjusting normals and faces?

Of all the things I've done in O2, getting those normals to face appropriate directions is the toughest. There seems to be very few options for them, and it's very important for many things. Anyone have any techniques they would like to share with us about adjusting normals and faces?

I wasn't too happy with the trivial improvements in 1.30 (new vehicles / weaons excluded), but 1.40 is an excellent, solid set of fixes and improvements. Finally some of the most critical gameplay problems have been addressed. The friendly fire checks and the team sighting bug where probably the most complained about issues of the past. THANK YOU BIS for finally addressing these issues. Now the only real complaint I have left is how the AI will continue to attack empty vehicles (including jeeps) and how the machinegunners always fire above them.

I wasn't too happy with the trivial improvements in 1.30 (new vehicles / weaons excluded), but 1.40 is an excellent, solid set of fixes and improvements. Finally some of the most critical gameplay problems have been addressed. The friendly fire checks and the team sighting bug where probably the most complained about issues of the past. THANK YOU BIS for finally addressing these issues. Now the only real complaint I have left is how the AI will continue to attack empty vehicles (including jeeps) and how the machinegunners always fire above them.

Well after many months the best mission submitted to the Codemaster's mission compo is now available. It is called "Changing the Guard" and is a whopping 20k download. My submission, Operation Firelord, was also entered into this contest and that was confirmed by the folks at Codemasters themselves. It didn't even place in the top 5. After playing this winning entry for the OPF Mission competition it is entirely obvious to me that my submission was not even judged! This winning mission would have recieved a 6/10 at any review site. It has a two sentence briefing, almost no dialogue, no character development, minimal story, weak camerawork, almost zero explination of the situation, almost no props, and nearly zero gameplay. WHat the heck was going on during the judging? I urge all of you to compare the missions and see for yourself. Here are the links to the missions: Codemaster's winning entry: ftp://downloads.codemasters.com/missions/change_of_guard.zip Firelord lite (Firelord without voice and music files) ftp://downloads.codemasters.com/missions Firelord full (With voices and non-copyrighted music) <a href="http://www.ofpeditingcenter.com/devilchaser/firelord.zip If" target="_blank">http://www.ofpeditingcenter.com/devilchaser/firelord.zip If</a> you agree that this competition didn't even judge my mission, please e-mail them at: Codemasters UK or Codemasters USA (Edited by Devilchaser at 1:56 am on Dec. 11, 2001)

It will be a while because, believe it or not, the two follow ups are going to be much more detailed and involved. #2 will play a bit like a detective game so it will be very open and I have to account for a million possibilities. #3 will put you in the place of the Firelords so I have to figure out how to let you levitate things and blow things up with fire. Not too tough to do the damage but allowing you to select targets will be tough.

Just to note, there is an announcement that there will be another patch this December. We can all hope!

I've also noticed a fair amount of serious issues are still not fixed. Yes, 1.30 is an improvement, but it has been played up as this "uberpatch" and it is not. It adds more than it corrects. Here are some serious issues NOT corrected: 1. Machinegunners always shoot above vehicles 2. Tank gunners fire over Jeeps and UAZs (possible other vehicles too) 3. Empty vehicles still cause AI units to attack them, and with the above problems the AI will waste gobs of ammunition trying to destroy an empty vehicle it can't even hit. 4. Tank gunners do not get the RADAR their commanders do. WHy is this important? Because the commander gives the simple order "attack tank" and does NOT tell what direction, etc. THe direction is only specified when a unit is first noticed. 5. Tank gunners do not notify commanders when a round is reloaded. Yes there is an indicator but in combat you need to be looking out the gunsight. 6. At long ranges, AI units choose to fire automatic weapons while standing and use burst mode in their rifles. A complete waste of ammunition. 7. At least in my version, there is no LGB model. 8. The A-10 dies by being shot by a SHilka for less than a second. Is this the most combat survivable aircraft in the world? 9. There is no AP round option for the Bradley. 10. THere are still serious one-way transparency issues with building and vehicle windows. 11. The grenade launcher sights are pointless and do not use an angled camera to facilitate aiming. 12. The G36a rifle has an offset crosshair. 13. Enemies are still locating targets and accurately shooting them through dense cover. I have noticed an improvement from 1.29, but I have also experienced these problems in 1.30. 14. "Heal at Medic" is mixed in with all the options, never on the very top, so in the heat of combat you must search through all your options before sending a teammate to the medic. 15. Medics do not automatically try to heal wounded soldiers. AI soldiers are not able to call for a medic on their own. 16. AI still responds very poorly to sniper fire, sometimes completely ignoring it. 17. Etc... Also, here are links to some bug-example missions I have made available. http://www.ofpeditingcenter.com/devilchaser/bug_example2.zip http://www.ofpeditingcenter.com/devilchaser/bug_mission.zip http://www.flashpoint1985.com/cgi-bin/ikonboard/topic.cgi?forum=19&topic=1185 So, I won't say 1.30 wasn't an improvement. It most definitely was. And I'm very grateful. But, honestly, there is much more work to do and I expected more out of it. Since the ultimate upgrade wasn't scheduled until December, I really hope that there is another patch in the works. OPF is much better now, but a ship with less leaks is still a leaky ship. (Edited by Devilchaser at 12:48 am on Nov. 15, 2001)

Thanks for all the applications folks. We are still looking to fill for all positions. So if you want to bring your talents to a higher level and contribute to something big, send us an e-mail.

Hi all. If you live in the European time zones and want to contribute to the OPF editing center campaign project, then we would like to hear from you. You will be working in a small team, creating one mission at a time that is given to you via our main story team. You will also be in touch with other departments depending on your specialty. These are the positions we need filled: 1. Advanced Scripter (1) 2. General mission editor (2) 3. Story / screenplay writer (1) 4. Cutscene creator (1) 5. Environmental editor (1) Substantial OPF editing experience and ability to work in a team required. Example missions a plus. Send all inquiries and applications to: Shogun (Leader, Euro3 Editing Team) [email protected] (Edited by Devilchaser at 8:16 am on Nov. 27, 2001)

I don't know about you, but I'm tired of watching my guys prioritize empty soviet vehicles and blow all their ammo on them, many times shooting straight over them anyway. THis happens with the M2 machinegun ALOT!. Also happens with the UAZ and Urals. Our missions are being ruined by this stupid AI behavior. I've had to use a trigger that destroys vehicles just to keep my AI teammates from blowing all their ammo on them instead of moving on and ignoring an obviously abandonded vehicle. So put a post here telling BIS that enough is enough!

YOu are right on the money guys. Looks like Obi Wannabe has issues to me. This isn't a thread about "the AI is stupid" if that was the case I would have just posted one sentence eh? It's about a legitimate concern that really fouls up gameplay. People like him are just fouling up our attempts to bring OPF issues to BIS's attention. DO us all a favor and keep your insults off the forums. By the way, please click on the below link. It will take you to my thread that has example missions I made for showing many of the current OPF bugs / glitches. See it for yourself. http://www.flashpoint1985.com/cgi-bin....ic=1844 (Edited by Devilchaser at 3:31 pm on Nov. 24, 2001)

THanks for posting here guys. Let's keep this thread alive so BIS can see some of these issues.

Well I'm talkin 1.20 for the hellfires. Haven't tested 1.30 so I guess they are missiong.

I have been seeing the Hellfires, and I have also noticed them leaving the helicopter as they are fired.

But unfortunately there is nothing to indicate wind direction

I had great luck with the sniper rifles. YOu set them to hold fire, designate a target, then tell them to fire. It's perfect. Thank you BIS for this feature!