Hi All,One week after placing my order with EpicMapper, I have yet to receive my installation codes despite three requests. Anyone else have this problem? I am about ready to call my credit card company.Cary

Sorry to hear this. BUT you should have used FS COMM. it's fast,has a good GUI and It is FREE...........

TVRON,Got the installation codes. I actually installed FSCOMM and liked the GUI - very easy to use. However, I want to compare it with EpicMapper before commiting to one for my project.Cary

Hi Cary, let us know how you like it. Ron.

HIWhy use Fs Communicator instead Epicinfo?What more?Regards

>HI >>Why use Fs Communicator instead Epicinfo? >What more? >>Regards That's a loaded question. for one thing you don't need to edit the fs config files, you can do some very cool scaling and you can assign any PH # you want. If you want to know more,read the FS COMM doc's. I love the program and it's free....

Hi Cary,I'm also very interested in hearing your comments - which of the two performs better. I think most of us have used only one of the two (EpicMapper in my case).Good luck,Hans

Hello Hans,Will keep everyone informed about my opinions (for what they're worth!). I worked with EpicMapper this weekend (still just using the landing gear switch) and succesfully mapped it (albeit had to use a ROTARY declaration (not BUTTON) in order to change the gear offset). While I like the FSComm GUI, EpicMapper's simplicity is very attractive. One major concern is performance of the middleware, and specifically its affect on FS2002 performance. I noticed you (Hans) have modified the timer settings in your EpicMapper config - how did you come up with these may I ask? Thanks for your continued assistance.Cary

Cary,I did not modify any timer settings. I use EpicMapper since V.1 and those values were in the config.ini since the beginning. Never had any trouble with the settings, so I left them unchanged.About the different sections: I don't know what Marc was thinking when he came up with the titles for the different sections, but this stuff is certainly not self-explanatory.Anyway, this is what the sections are for:- "Button" is for toggeling of offsets- "Display" is for reading offset values (from PH's)- "Rotarty" is for writing values to offsets (with nqw's)All the best,HansPS: Maybe Marc Teichtal could shed some light on the differences between EpicMapper and FS Commander...?

Hiya all,I thought id drop in and throw my 2 cents on the table....Im glad to hear that most of you are having success with EpicMapper.In direct relation t Cary's comment of needing to use a ROTARY rather than a BUTTON for the landing gear. Firstly, Pete Dowsons SDK document should be your bible. In terms of the way we handle the landing gear lever; this is a 4 byte offset at 0BE8 with 0=Up 16383=Down. Whilst writing the code everyone in the beta team insisted on following this scheme. Hence, most people have implemented the landing gear lever as ROTARY rather than a BUTTON. However, you can also use a BUTTON by ensuring you send nqw_data of 0x00 for LG UP position and 0x3FFF for LG DOWN position.The main point to remeber here is that a BUTTON *toggles* a bit in an offset and a ROTARY sends changing data to an offset.

Marc,any comments on the differences in the "inner makings" of EpicMapper and FS Commander, especially concerning system load and FS performance?HansPS: I remember EpicMapper V.2 was due 1Q 2003. Do you have a new ETA and some info on what will be new (can't think of much, because V.1.1 does what it is supposed to do quite flawlessly)

Hans,Please see my other posting in this forum entitled "EpicMapper - Thoughts and Evolution"There are some comments in there that may satisfy you. If not let me know and Ill post more details.