Japo32

It will be great if you work on sounds... but I believe being 2 years and a half of continous work I don't call it too early!!! believe me it was released on the right moment.... Now or never (I know this veeeeeeeery well)

Mmmmm I wonder what we are doing wrong?!!!!! Every user that has the same problem are going to post their own same problem? Cameron is there a way users has to read the sticky posts before posting?? Urbanex... hehehe.. well... I think you won't have any problem finding the solution to your problem. Thanks anyway for your purchase

Dancemad... we said that the tester didn't test the performance.. just that if you were going to have problems with opengl.. But it really works, because you are running it. To make a performance tester we then had to load all the systems inside the CRJ and load the polygons and textures of the CRJ.... and that is the CRJ. But we cannot release a demo of it, because we didn't have any time limit program. Also I published 3 different configurations to clarify everyone what they could find, and told that usually you loose 50% of performance once systems are running inside x-plane. You have the plane for always, so maybe today you cannot fly it correctly but as soon as you change your computer to a better one then you will be able to fly it. This is something very well known by PC gamers. Latest games are made for good systems, so they always know that if they have a computer 2 years older than the released game, they will have probably bad performance. If you have really nice performance on x-plane, that doesn't mean everything you are going to load in it, it is going to go well. If somebody has 24 frames on normal default planes, then he/she, cannot prettend new planes with full systems go the same way. well, as said, you have the plane for always, and you will be able to use it perfectly when you have a new system (and it hasn't to be the most high end one. Of course the more power, the better).

Check what layer property I used to each color later. multiply or overlay... Don't remember right now.

Yes, follow the same way I did them. That is why I left them there

Ah!! You didn't see it because he edited the post. He has put later the link. Sorry cannot copy paste right now. I am on phone. Hope it work for you. If work ask me the datarefs of fms buttons.

Follow the same way as the examples included. They are made with plain colour

I think Philipp just said that is not possible to work on that. Being payware doesn't mean we can solution all problems of costummers. If for example someone don't have a good computer and he has low fps, then we only can tell that person to update his system. We will work hard to verify that the main crj works correctly, even with some external variables as the x737, but we cannot buy all computers, or hardware around. We will help people that has those external hardware understand the plugin to let them program drivers for it. But we cannot make the programming for them. It is not policy of us. It is just we haven't the money and time to do that. I know it can be frustrating to owners of opencockpits, saitek yokes or whatever, but you have to understand that we are not gods, even if people pays for doing what they want. You can critice. Of course as costumer, but that doesn't mean a costumer is always right because paid for something. Anyway, we will publish the datarefs names, and with the posted plugin you can use them as keystrokes.

Did you try with the clean demo of xplane? Maybe that way your instalation remains... Hope you can solution this one soon.

And ubuntu? It is tested there, so maybe it is better to know if because of Os or not... Edit: ahh i saw also opensuse was tested. Sorry

Hola Boke. The reason I put it on nose was to hide a cable plugged directly to fuselage without any open door. It was not planed from beginning to make the gpu, soni found a good solution do it on front wheel compartment

Thanks Simon, will try to fix it. Not easy one because even on blender is ok, sometimes position of polygons in xplane are not the same. So many wars with that issue.

About the "e" key in the fms and others difficult to key. A solution will come on next patch. About buttons to program, we will provide datarefs names so anyone can program hardware to manipulate them.

Hi! Looking ar your hardrware settings is normal,it goes not quite well for you. A dual core under 3ghz, and the 9800gt a graphic card that was good, but some years ago, cannot make the work well done. So I suggest you update your hardware settings. I know maybe other planes runs great for you, but those planes uses too much genetics. Her we have 2 plugins running parallel, that needs be distributed by cpu quick to gpu. So, this plane cannot be compared to any before of this, even if I made them (mentor, seamax...)

we have just made a bug solution about this Thrust limit bug, on the next 1.1 version. I have tested it and seems to be ok. BUT for me it was already also ok... But philipp found something.

yes you are right. Not all knows about complexity of x-plane... but also I like to put solutions for everything here on forums.. on sticky ones. I will put this new one on the stiky.

Sure! And you are free to post whatever you like. I just defend our plane. Trully we are the ones that knows what is simulated or not, and believe me autopilot is much more complex than default one, so when when you said that they are the same as xp, i just want to inform that that is not real. Only that :)

As said, red, not done, so I don't know why you made such expectations. But autopilot is not the default one. It has programing inside, joined with the Fms. I think that worth 60$. About future implementations? I said that if it is possible they will be done, same price. I don't promise not because I don't know if they are posible to do, but because we can recover the work done. But price is not only set because systems done or not done. More considerations are inside. Some people thinks the plane is very expensive for what it offers. Others thinks it is even very cheap and worth every penny inverted. People is free to buy it, and I released the manuals to tell people what is simulated and what not. I think is fair. I would say you Tobs just fly it and enjoy it.

Activate pixel shader inside renderings. Because you are not using them the 3d engine is not using normal maps, and more important specular maps so everything is brighting the same lever

ok.. I better delete the files.. I made.. Less to download. More space here.

Opened here right now and the work. If they worked also for Kesomir, then they are ok. I believe you have a problem with memory, maybe. Fuselaje (fuselage), and alas (wings) are big ones... maybe because of that you can't. I will include a only png file also on 1.1 in case people cannot open them because they are heavy.

Maybe is a problem of your copy of CS5. A user already made a paint already on the org for free.. so he had no problems with it I believe.

First you have to select runway then SID. It is inside the manuals. if you select first the runway then you will be able to select the SID (not the other way), but when you select the SID when a different page that first one.... all disappears on SID side. You have to press Prev Page to reach the first one. You will see selected the SID you chose, if everything is ok.

Ok.. do the changes you have to make.. and if so... I won't put them inside the pilothadbook.. BUT because I think exel files (and yours I think it will make it, make calculations inside... so better to leave it as a exel file. I will put it inside documents. So make it beautiful and if you make it before 1.1 version is out, then I will be glad to include it!

of course I know there are some people that can wait, but others not. Usually those than not is because everything is working correctly for them so they want the plane to be increased in functions. But I just want inform all that for sure we will make more functions on future (if possible on team), but first we must ensure people that are having important bugs that don't let them fly the plane, get all resolved. So I just wanted to inform that this next 1.1 version will be mostly for bugs resolving. There will be little improvements also, but not so few.