Lost_in_Isaan

Getting closer, replaced all the 139_xxxxxxx.bmp files with the originals. Colors back to where they were some time ago but I'm thinking global and vector enhancements have been removed. Displayed is a grass land enhancement (resolution) in the FTX Aero (REX) pack. detail1.bmp file, just for information.

I've looked at that, it's just a resolution upgrade of the detail1.bmp file. Not an actual grass replacement. Whatever the problem is it's either overlaying the taxi_grass_xx.dds files in the texture folder or the Land Class 95/96 GRASS_SKIRTING - bmp files 139 and or 140 eg. 139b2fa1.bmp in the \..\scenery\world\texture folder.

Thanks again Robert, as I said, I will not let it beat me! If I can find the default location for the airport grassland *.bmp or *.dds files that would be a great start.

Robert, I have sent the file. Thank you for your efforts. Peter, no I am not using GEX. I had this grassland installed prior to (many years) buying Global/Vector.

I can't remember, other than I did!! I'm sure if it was an installed addon I could find it in the Addon Scenery folder. If it was a texture change I would have backed up the originals as I'm normally paranoid about thoes sorts of things. Wasn't really a problem until I installed ORBX Global and Vector after which it was obvious this grassland (photogen) texture should not be there.

I've corrupted the grasslands of all my default and self designed airports with an overlay that I can't find now. (Payware airports are OK). Been through all the folders I can think of eg. Addon Scenery, Scenery, Textures, etc. tried different detail1.bmp files (only changing the resolution of runways, taxiways etc). Does anyone recognise this and where to get rid of it? Edwards AFB but ALL airports world wide are the same. Thank you.

Well, I can say both packs are well worth the investment. My only gripe was with the plss poor response (zero) I received from both ORBX and FSS over issues I had with corrupt files on the DMS DVDs I bought. http://www.orbxsystems.com/forum/topic/77799-need-help-with-some-corrupt-files/

I have recently bought the B29 (it's not an A2A B377 but really enjoying the challanges) and in days gone by the F-111 and B1B. "Value for money" all very well worth it. On searching numerious sites I cannot find a forum where simmers with Virtavia products share their experiences and tweaks, can someone point me in the right direction. Thank you.

I rest my case, what a farce! Deserving winners --- yes, BUT 7 votes each. Gimme a break! After recent events I, for one, am becoming more disillusioned with ORBX and one of it's major vendors.

I'm in the process of writing an XML routine for a high performance aircraft but find when using the command: if{ @VSIOffset 1200 + (>K:AP_VS_VAR_SET_ENGLISH) } the @VSIOffset macro result is a computed value up to 20,000 meaning I need the aircraft to climb or dive at that rate, for a short time. The maximum vertical rate the AP system will take is 9900 feet per minute in either direction, is there somewhere I can increase this value, scratched around in most common places and can't find it. Thank you in advance.

As you may know they are currently running a photo competition based on their NZSI package, with a reasonable prize. I found it very humorous to see they are having problems getting votes in. IMHO obscure rules where only the participants can vote (not for themselves), no one can cast comment, forum members including NZSI license holders have no say. Needless to say I and others did make a comment which stayed up for a few hours before deleted. BTW, I did not enter being the 'worlds worst photographer' even with a 'v' key. I say to JV:- If you can't get the entrants (about 30 of em) to show enough interest to vote why not open it up to all members. At least you will get realistic result rather then 6 votes for 'Harry' 6 for 'Jack' 4 goes to 'Mary' etc. because from what I have seen that's all your getting. And, if nothing else you can't delete this!

Just to be technical I don't think we OWN the software we have just bought a license to use it. Anyway all the regions, Lancair (don't fly it much) and a few airports. I think it's 17 orders in all. My dinosaur of a computer hates ORBX airports (not their fault, I love em) even with the sliders hard over to the left.

OK, couldn't get much help so with trial and error I managed to get these formulas working perfectly in XML to give me accurate track co ordinates at any distance in front of my plane.Solving the problem above was down to basics, I just simply used this in lieu of the incorrect TAN value.tan = sin(lat1) / cos(lat1)I was then able to solve these.R = sqrt((((a^2*cos lat)^2) + ((b^2*sin lat)^2))) / ((a*cos lat^2) + (b* sin lat^2))lat2 = asin(sin(lat1)*cos(d/R) + cos(lat1)*sin(d/R)*cos(track))lon2 = lon1 + atan2(sin(track)*sin(d/R)*cos(lat1), cos(d/R)-sin(lat1)*sin(lat2))Now if only I can have FSX return the terrain altitude at any given navigation co ordinate as it does with the (A:RADIO HEIGHT, feet) variable beneath the plane I'll be almost there.Any ideas or even hints from the experts will be appreciated.

Haven't been banned but <Edited by Mod> after I aired a comment on his business strategy a few years back. Alas, as has been stated it's his products, his forum and his decision on how they should be managed. With products the likes of NZSI he can call me whatever he likes, I'll still buy.*Took out a non family friendly term and the mention of individual using it.

It’s the olde flogging horse: Feed forward or Derivative information to make an Auto Terrain Follower work getting accurate forward TRACK co-ordinates and Altitude info. Was inspired to resurrect it after buying the DBS Profiler package, they seem to have the problems sorted. Been working on it for years (on and off) and getting very close but have a problem with the way FSX presents the true value of the TAN of the degrees (Radians) of Latitude.The last equation I need to solve is simple:The TAN of the Latitude squared minus 1 ---- in XML looks like this (simplified):(L: TAN_TF_LAT, number) (L: TAN_TF_LAT, number) * 1 + (>L:Factor_Nm_MUL, number)and that gets shoved into the end calculation. BUT, for example the trig tables for the TAN of the angle (latitude) of 30 degrees is 0.57735 which on paper works perfectly for my solution ----- but this XML command:(A:GPS POSITION LAT, radians) tan (>L:TAN_TF_LAT, number) returns a value of 0.52347 the discrepancy is creating all sorts of hassles.The nearest ‘Bandaid Solution’ I have found looks like this but it’s bullshlt and after 79 Degrees North or South forget it:“Near to real” TAN = 0.94 / cos latitude * tan latitudeOK, where are the numbers men/woman?Thanks.