Hi Guys,
I figured it would let the X10 beta thread play around with BETA4 for a while, just to see what new issues pop up. I have made some feedback below (mainly calls for more info). The only issue I can act on since my last post was the one from Science Boy (medieval pack misbehaving and anti-grav platforms not following waypoints after 2 levels). Here is my feedback:
JBoy77 : In V109 we fixed the water movement so that it is not based on cycles, but time which means it is now consistent no matter how fast the frame rate is going. Prior to V109, the water movement was bugged.
Soviet176 : I need to reproduce the blue screen or I cannot fix. You will need to provide me with the FPM of the level that shows this issue, and a step by step of what I need to do to reproduce. Also tell me which model packs you are using as we do not have sewer graphics in the default media for X10?
science boy & JohannesM : Model Packs where never designed for ragdoll, and to retain functionality we added code to ensure model pack characters do not attempt to use ragdoll. There should be no expectation of new features or enhanced functionality when using model packs in X10, merely that they perform as close to X9 as possible.
Squalker : I cannot detect a change in performance between beta3 and beta4. Can you provide an FPM and a step by step of how you compared beta3 with beta4, and give me your frame rate results on both tests. Also provide specs of your system so I can do a relative comparison with my own system as it could be hardware related.
Soviet176 : Please attach your screenshots to your post as JPG files. The links you provided are broken. Just as a note before I can study your screenshots, if you are getting good framerate and then drop right down, ensure that part of your level has no holes to the outside universe as this can often result in the engine rendering the whole exterior structure and slowing you down.
Soviet176 : There are no plans to enhance shader support in X10, nor support earlier shader model 1/2/3 as used in X9. You do have access to customised shaders, but you will need to study the 'customeffect' example and remember you have to use Shader Model 4.0 that conforms to the basepool.FX shader code provided for compatibility with the X10 engine.
Nilloc : Please provide an FPM, and a step by step how I can reproduce this blue screen. Also indicate if you are using any third party or model pack media in this level.
Notunknown : Please install the latest version of DirectX to avoid the d3dx10_40.dll error.
immortal : Please provide an FPM, and a step by step describing exactly what you expected to see and what you actually saw. Also provide a shot showing the missing water and let me know if this is a fresh X10 installation or if the files have been manually modified in any way. As to the serial code issue, ensure you are running in Administrator mode and that you installed in Admin mode too, and also ensure UAC is switched off. If you are using FPS Creator X9 at the same time as X10, this may cause your code to be wiped. Alternatively, try entering your code inside USERDETAILS.INI so you do not have to enter it manually each time.
Bigsnake : The tech demo was a very early prototype, and some features did not make it into X10. We are not planning to add any new features to X10, instead focusing on stability and consistency.
If you find an issue, the best three bits of information I can use is an FPM, a screenshot and a series of steps I can use to reproduce. There might even be a fix in it for you
I drink tea, and in my spare time I write software.
