Aces High Bulletin Board
Help and Support Forums => Aces High Bug Reports => Topic started by: KG45 on July 12, 2008, 02:51:03 PM
-
not sure if this is place to put this.
and it may have been posted elsewhere but,
at V203 there are 3 arrows to nearby bases but only two buttons on the clipboard.
-
I can't tell which map you say this bug is on, can we get some fication from clara?
I know I have no map titled TAGMA.
-
go to blue arena
-
I can't tell which map you say this bug is on, can we get some fication from clara?
I know I have no map titled TAGMA.
I do now, though.
-
TAGMA also had RV8 enabled, and sdk and p-39s disabled (new planes added, old plane list saved?)
-
Another Bug with TAGMA map! Taking off with formation of B17 to the NE lost drone #3. Didnt think much of it. Next time I looked and Drone three turned around on Runway and took off to SW. Took off fine when whole formation took off to SW.
-
KG45,
Here in the AH2 Bug Reports forum is the right place to report these things. Spawn point buttons are based on the direction you will be facing when you span. Two of the three spawn points are facing in the same (SE) direction. Thanks KG45.
(Note: Vehicle entry point F203VHE001 should point east -- not SE. The Check Entry function in Terrain Editor, Version 2.10 Patch 2, only detects if there are more than one entry point pointing in the EXACT same direction. At least this is the way it appears to be working for SE spawns. The Check Entry function should check for more than one spawn point pointing between 112.5 and 135.5 degrees for SE spawns.)
--
Krusty,
All fields are supposed to be set to Standard. The most current version of the Terrain Editor (AH2EDIT2101.EXE, 5/10/2007) does not include the latest weapon systems like the sdk and P-39. It was hoped that the field settings would get updated as the terrain got prepared for the MA. If there is a way to add the new equipment to the Terrain Editor, let me know.
--
spacer,
It would be helpful to know which field you had this happen. This problem used to be caused by not having the tile’s subtypes under the field set to 0 (zero).
-
Krusty,
All fields are supposed to be set to Standard. The most current version of the Terrain Editor (AH2EDIT2101.EXE, 5/10/2007) does not include the latest weapon systems like the sdk and P-39. It was hoped that the field settings would get updated as the terrain got prepared for the MA. If there is a way to add the new equipment to the Terrain Editor, let me know.
I don't know about the TE, but Skuzzy or Pyro can fix this without reworking the map. I think they just need to set it then save a table for it, then every time the map loads they load that table. This being the first time, there was no table to load, but it's definitely something you can fix in the arena settings.
-
OOOPs! Sorry, I had the info for the take-off problem on my little note! Just forgot to put it in here! :cry
The base was A157. I did not try any other bombers to see if it happens to them too! ( All for one, One for all?) Will try if Knights still own the base!
-
Well I tried it with some B-24s on A157 it did the same thing. #3 drone took off SW when trying to launch NE. It does the same thing at A190 #3 drone launches SW no matter what.
-
The planes and vehicles missing are all fixed now.
-
spacer,
Thanks for the info. I checked the terrain in the Terrain Editor and the subtypes are set to all zeros for both A157 and A190. Back when the tile subtypes under the field was causing this problem; it would do the same offline. I tried both of these fields offline in 17s and 24s with Auto Takeoff on and off and did not have a problem. Do you lose the #3 drone offline too?
--
Skuzzy,
Thanks for fixing the missing planes and vehicles. On the spawn point problem, are you expecting me to submit an update? Not sure how we keep from stepping on each other’s changes.
-
If you have something fixed, go ahead and send it to me.
-
MachNix I just tried it off line at numerous bases. Funny the only base it did it on was A157. A190 launched ok off line. Too many bases to try them all, but I did try a few of each type in the NW area of map off-line.
-
spacer,
No need to do them all. Just try the ones that did it to you online.
I will look at A157 and see what is unique about that field and make some changes. Unfortunately, since A157 works okay for me offline, I won’t know if the changes I made fixed the problem until the terrain goes back up.
Thanks for taking the time to report the problem and checking offline. <S>
-
Did you have a chance to find out what was causing the problem with the drones, or is there any confirmation from Skuzzy on the subtype issue?
Based on your statement about the subtype problem, I pulled and zeroed the appropriate tiles on a terrain that's waiting for Skuzzy, but I'd like to know if it's really necessary for my future work.
-
Here is some background:
http://bbs.hitechcreations.com/smf/index.php/topic,149210.0.html
I did not find anything unusual with the fields. The subtypes under the fields where set to zero, the terrain was level and set to grass, the fields where centered, at the same elevation as the terrain, and non-rotated.
I have not heard anything from Skuzzy about this particular problem, and I never heard anything about the original subtype problem being fixed. I always set subtypes under fields to zero and have not gone back and tried repeating the situation to see if the problem would repeat. This is the first I have seen where zero subtypes did not fix the problem and there was a difference between online and offline. Apparently a terrain that works offline does not guarantee that it will work online.
-
Thanks MachNix. I noticed that Pyro never came back to confirm the problem was caused by the subtypes, and as you checked everything else it's still a mystery. The Terrain Team hasn't noticed subtypes to cause these problems, but that doesn't mean it wasn't an issue, could be Skuzzy's tools would catch it as an error and repair it.
Thanks again
-
Hi Guys
Was upping Bombers from A190 on TAGMA again today 26 July and drone/s took off the wrong way again. Saw another guy have the same thing happen. Just letting you all know its not fixed yet. :salute
-
spacer,
A terrain update (15 Jul 08) has been sent but has not been put online just yet. Since sending the update, another bad spawn point was found that will require another update. I would like to wait until the map is won before sending what hopefully will be the final update. So, if you see a map date of JUN 08, expect to have problems with drones at A157 and A190.
It is also possible that you will always have problems at these two fields. I have tried both of these fields online and off, and the problem does not happen to me. I have made some changes to the sub-tiles but that may not be what is really causing the problem. One would think that if the problem was something on your end, like a sound pack or using auto takeoff or bomber loading, that you would have the same problem at all the fields and not at only these two fields. If it was something wrong with the terrain, everyone should have the problem and not just a few.
I would like to get this problem to happen to me offline so I could do some testing. I have tried using the B-17 with different loads, auto takeoff on and off, and different flap settings without experiencing the problem. What is your bomber configuration and takeoff technique? Do you hold the breaks until you are at full power? Do you lift the tail or hold back pressure to engage the tail wheel lock? Do you leave the number 3 engine off and just take off with engines 1, 2, and 4? Of course none of that is supposed to have any impact on losing the drones but obviously something is going on.
-
Machnix
Hi I use Auto takeoff, dont hold brakes or play with power (full on). Bomb Load is usually, 12 500 lbs. Maybe it could be something in my map download. I wont complain anymore till the map is updated again. :rolleyes: Will just keep it in the back of my itty bitty head, not to launch NE from 157 and 190 till then. Thanks
-
spacer,
A terrain update (15 Jul 08) has been sent but has not been put online just yet. Since sending the update, another bad spawn point was found that will require another update. I would like to wait until the map is won before sending what hopefully will be the final update. So, if you see a map date of JUN 08, expect to have problems with drones at A157 and A190.
It is also possible that you will always have problems at these two fields. I have tried both of these fields online and off, and the problem does not happen to me. I have made some changes to the sub-tiles but that may not be what is really causing the problem. One would think that if the problem was something on your end, like a sound pack or using auto takeoff or bomber loading, that you would have the same problem at all the fields and not at only these two fields. If it was something wrong with the terrain, everyone should have the problem and not just a few.
I would like to get this problem to happen to me offline so I could do some testing. I have tried using the B-17 with different loads, auto takeoff on and off, and different flap settings without experiencing the problem. What is your bomber configuration and takeoff technique? Do you hold the breaks until you are at full power? Do you lift the tail or hold back pressure to engage the tail wheel lock? Do you leave the number 3 engine off and just take off with engines 1, 2, and 4? Of course none of that is supposed to have any impact on losing the drones but obviously something is going on.
Just wondering why auto-takeoff would have anything significant to do with it?
All the Best...
Jay
awDoc1
-
Okay was able to duplicate the problem using auto-takeoff and it appears to be some combination of auto-takeoff, preloading textures, and tile/sub-type that causes the problem.
If you use auto-takeoff and do not preload textures, you will most likely lose the #3 drone the first time you launch but it will happen again depending on the tile's sub-type. After that, you are more likely to lose the #3 drone if the throttle is not at idle when you launch to the runway.
I will check to see if there is some combination of tile sub-types that will keep this from happening.
-
After some testing, the problem of loosing the #3 drone has a terrain elevation component as well as tile sub-type when using auto-takeoff. If the center vertex (the blue plus sign) of the tile on which the drones sit has a difference in elevation between -13 and -3 feet (-13 <= deltaY <= -3 ) from the field elevation, I did not find a sub-type combination for that drone tile that would prevent the #3 drone from rolling backwards. But I did not try every possible combination. There where some combinations where the drone would roll backwards when that drone center vertex was at the same elevation as the field (deltaY=0).
On the Tagma terrain, the drone center vertex for the NE launch of A157 is 3 feet below the field elevation. For the NE launch at A190, the drone center vertex is 5 feet below the field elevation. The SW launch for A190 is 29 feet above the field and I did not loose any drones.
My plan is to check the drone center vertices and set the ones that are in the "trouble" range (-13 <= deltaY <= 0) to either -14 feet below or 1 foot above the field elevation, and not worry about the sub-types.
That is all I have to say about that.