XNA Posing Studio XPS 11.8.8 -- Thumbnail Edition -- release 188

XNA Posing Studio XPS 11.8.8 -- Thumbnail Edition -- release 188

Download http://core-design.com/community_xps.html

Download link XPS 11.8.8:

Idea inspired by


What's new?

1. The "File-->Load pose ..."   window now has a preview image function!
2. The "File-->Load scene ..." window now has a preview image function!


It is easy to add!
Every time, if you save a pose or a scene, XPS 11.8.8 create the thumbnail preview image into the poses or scenes folder.  
All you have to do is to enable "Thumbnail View for Pictures" in your Windows explorer (Load pose / scenes window)
Hint: Thumbnail Previews Not Showing in Windows 8/10 Explorer  

How to enable Thumbnail Previews?:

What's also new?
Some porters have not added preview images for models, although this feature has been in existence since February 20, 2014  (XPS 10.9.8.7.6.5.4.3.2.1.0 - Countdown Preview Edition); although their description mentions something else:

Example:

3. By saving a pose or a scene, XPS 11.8.8 will add a preview image for the selected item into the models folder, if it is missing.

Thanks for the update...

Hi all ! I have a little question here, Is any way to avoid the bone limit (per mesh) when exporting from xps ? On max or blender I don't have that issue, but xps itselft has it, so I edit so material, export for save the work, but when importing the model is split into many pieces. I hope you understand my question with my bad English.

Congratulations on the update, and thank you very much for the work.

Hi! I just wanted to thank you properly for your hard work on improving XPS! Keep up the good work!!  
I have a question about the latest update. Would you consider making optional the following feature, please?: "Model folders that do not contain models are now moved from the "data" folder to the "WIP" folder."
I have a lot of folders which contain, e.g., only textures and I prefer keeping them in the folder along with the model.
It's just a suggestion!
Thank you!

OmezamenoKoucha wrote:Hi! I just wanted to thank you properly for your hard work on improving XPS! Keep up the good work!!  
I have a question about the latest update. Would you consider making optional the following feature, please?: "Model folders that do not contain models are now moved from the "data" folder to the "WIP" folder."
I have a lot of folders which contains, e.g., only textures and I prefer keeping them in the folder along with the model.
It's just a suggestion!
Thank you!

Hi Sara!
I just wanted to say that I like your renders. Especially "What's mine is yours".

Just saying:

I do not consider to make this feature "optional". Nice to know that you prefer keeping "texture packs" in the folder along with the model. I do prefer the same; and I keeping them also in the folder along with the model, as Brodway "texture pack".
Doing that without using the "Broadway Edition" double dash Notation, is not how XPS working. And XNALara had never works with this.
I call "porters", who try to sabotage XPS on this way, as "stupid".  It was one of the reasons why I had stop to continue to improve XPS, 2 1/2 years ago: https://www.deviantart.com/comments/1/633121343/4219205623
Since XPS 10.9.3 (Nov 21, 2012), there is a "texture pack" feature (Broadway double dash Notation) to keeping the additional textures in the data folder, along with the model. Nobody in the last 7 years has dislike it and nobody since 7 years requested to Change it.
Use it or do not use it. It is your decision.

Thank you kindly for liking my renders!!  
By writing "Dusan Pavlicek/XNAaraL", I just wanted to credit both you and Dusan... I'll write it properly, following your hint.  
What I wanted to say is that some subfolders (e.g. folders containing unconverted models or folders, that are not renamed according to the "Broadway version") have been moved to the WIP folder by default. I'd like to choose whether to move these folders in the WIP one or not.
I'm not asking to change the "texture pack" feature, because it's very useful! My suggestion was to change the behaviour of the WIP folder, by adding the possibility to use the WIP folder by choice and not by default. This way, folders and subfolders can remain in the original position (if preferred), or be moved to the WIP folder.
If it's not possible, it's ok!
Thank you!

OmezamenoKoucha wrote:What I wanted to say is that some subfolders (e.g. folders containing unconverted models or folders, that are not renamed according to the "Broadway version") have been moved to the WIP folder by default. I'd like to choose whether to move these folders in the WIP one or not.
I'm not asking to change the "texture pack" feature, because it's very useful! My suggestion was to change the behaviour of the WIP folder, by adding the possibility to use the WIP folder by choice and not by default. This way, folders and subfolders can remain in the original position (if preferred), or be moved to the WIP folder.
If it's not possible, it's ok!
Thank you!

I already understood your request in your first post.
You misunderstood my answer (I know that my English is difficult to understand).

I will answer your question in other words. Maybe that will make the facts clearer.

<< You want a way to prevent folders without having a mesh (model) from being moved to the WIP folder?
>> This way exists already. There has been a way to deal with folders without having a mesh, without cause a problem, for six and a half years (since XPS 10.9.3). I call this way to avoid the "move to WIP" folder , a "texture pack" feature (e.g. the folder is marked with " -- ").

<< You want to request, to extend the XPS 11.8.7 feature "Model folders that do not contain models are now moved from the "data" folder to the "WIP" folder."? By adding a "choose" dialog to use this feature or  to not use this feature?
>> This is possible. It is easy to implement it. But I don't want to change this behavior.

I don't want to change this behavior for different reasons:
1) Inside the "data" folder belongs only model data folders
2) Folders and subfolders (without mesh and only textures) can remain in the original position, like you prefer, if the porter (or you as user) make it right. That is the "texture pack" feature. I explain it later.
3) "Model" folders without model data do harm the application; and do confusing the users; and cause warnings.
4) folders and subfolders can not remain in the data folder (even if you prefer it),if this folders contains no mesh file. This folders (e.g. folders containing unconverted models) must be moved to the WIP folder.
5) There are some other reasons too.

I'll write an example to show you what you can do that folders and subfolders can remain in the original position.
You use as model "Lunafreya". At first I thought you had used the wonderful model by NightysWolf:

Lunafreya for XPS by by NightysWolf:

That was not true.
The model you used had another "additonal textures" folder on the same level as the "Final Fantasy Lunafreya" model folder. The folder "additonal textures" had 3 subdirectories "Default", "Injured" and "Pale". Right?
So, the whole tree "additional textures\Default", "additional textures\Injured" and "additional textures\Pale" was moved to "WIP\data" folder. Right?

My solution is:

There the DOWNLOAD link:

fixed Lunafreya for XPS:

What have I done to fix it?
1) The different appearance of Lunafreya are inside a folder "Final Fantasy". In this folder is also a "preview image" (Prev.png). This folder  is not required, but it is recommended.
2) Inside the  "Final Fantasy" folder is the subfolder with the model (mesh), named "Lunafreya", and a "preview image" (Prev.png). This model folder is self-evident required!
3)  Inside the  "Final Fantasy" folder are also the three folders with the additional textures, "Lunafreya -- Default", "Lunafreya -- Injured" and "Lunafreya -- Pale". Note the necessary naming for XPS: "Model Folder Name", "blank hyphen hyphen blank" and "texture pack folder name". Each "texture pack" folder has also a "preview image".

What are the advantages of this solution?
1) You can load the "additional textures" (texture packs) like a normal model, using "File-->Add item(s) ..." or by Drag&Drop the texture pack folder into the 3d Window; without needs to use the "Material Editor"
2) You already see in the preview dialog what the additional textures look like
3) Folders can remain in the original position
4) If you want, you can use the "Material Editor"
5) No warnings about "Data folder "data\foo\textures" contains no mesh file. Skipping... "
6) No waste of memory space (RAM)
7) Better performance
...

Izack wrote:Hi all ! I have a little question here, Is any way to avoid the bone limit (per mesh) when exporting from xps ? On max or blender I don't have that issue, but xps itselft has it, so I edit so material, export for save the work, but when importing the model is split into many pieces. I hope you understand my question with my bad English.

Congratulations on the update, and thank you very much for the work.

I understand your english, but I don't understood your problem.
You really should update your XPs version!

XPS has no bone limit since Oct 15, 2012 ("XPS 10.9.1 - Bones unlimited edition")
XPS do not  have that issue,
XPS do not split a mesh into many pieces (Except you save it using "as old generic format". This is the only option which has to split the mesh, because every old version before XPS 10.9.1 had this limit)

(3ds) max have that issue! Or more precise, the max exporter by mariokart64n do split meshes

max XnaLara Converter by mariokart64n:

You really should update your XPs version, it is outdated for six and a half years!

Wow, many thanks for your answer. It is very clear and enlightening!  
I don't use neither NightysWolf's nor Xelandis' models (not the latter ones anymore), because I ported FFXV models myself, but your example has been really constructive. I'm going to adjust folders and subfolders this way.
Sorry for misunderstanding your previous answer.
Thanks for taking your time to write the above!

Hi XNAaraL, thanks for answer. Yes I export the model in .mesh.ascii format and that happens. I always use the latest version of xps, its not 6 years old hahah

P.D: I´don't like the wip folder... just ruin my way to do things.

Wow awesome. I still hope for a principle render material will be add to support rendering human skin
Haha

ngovandang1997 wrote:Wow awesome. I still hope for a principle render material will be add to support rendering human skin
Haha

Haha, I like this joke.

ngovandang1997 aka TheForgottenSaint47 aka Dangel-Deviliono. Seriously:
Since Feb 20, 2016 (XPS 11.5 - Seven Anniversary Edition), this is possible.

"Render Material" is generated in XPS as a "shader" effect. XPS has an "Application Programming Interface" (API) to support new third-party shaders.
Subsurface scattering shaders (SSS) for skins or wax can you just add to the "shaders" folder.

SSS:

XPS 11.5 wrote:-> User written shaders written in the HLSL language can be added now!
Three demo shaders, with eight Techniques (example for developers), are included inside the new shader folder "XNALara_XPS\shaders" and are called "XL GrayScale.fx" , "XL Sepia.fx" and "XL Shading"
When started, XPS read this shader source files and compile the source code. The menu items in the "Shader" menu will be added.

BTW:

> 360°:

XNAaraL wrote:

ngovandang1997 wrote:Wow awesome. I still hope for a principle render material will be add to support rendering human skin
Haha

Haha, I like this joke.

TheForgottenSaint47. Seriously

  How do you know that's me

ngovandang1997 wrote:   How do you know that's me

Special for you my friend, YOU can get your SSS shader here https://www.deviantart.com/vincentxyooj/art/Blender-Cycles-Skin-Shader-NOW-AVAILABLE-511446296

VincentXyooj wrote:This is a universal skin shader for
blender that works on DAZ, XPS, etc...

VincentXyooj wrote:https://www.deviantart.com/comments/1/511446296/3906692639
You are able to tweak the sss and everything with my shader, the possibilities are endless , works with any skin tone  
that you can think of :3. I made sure that it could be used for anything.

Spoiler:

XNAaraL wrote:
Special for you my friend, YOU can get your SSS shader here

Thank you alot then

Izack wrote:Hi all ! I have a little question here, Is any way to avoid the bone limit (per mesh) when exporting from xps ? On max or blender I don't have that issue, but xps itselft has it, so I edit so material, export for save the work, but when importing the model is split into many pieces. I hope you understand my question with my bad English.

Congratulations on the update, and thank you very much for the work.

Izack wrote:Hi XNAaraL, thanks for answer. Yes I export the model in .mesh.ascii format and that happens. I always use the latest version of xps, its not 6 years old hahah

P.D: I´don't like the wip folder... just ruin my way to do things.

Che boludo, ¿qué hacés?

At first

Izack wrote:Congratulations on the update, and thank you very much for the work.

Izack wrote:P.D: I´don't like the wip folder... just ruin my way to do things.

These two statements from you sound totally contradictory.
P.D: Non model data inside the data folder, just ruin the way like XPS (and XNALara) to do things.

Data folder "data\foo" contains no mesh file. Skipping ...:

2nd
Random XPS user: XPS has a bone limit (per mesh) when exporting
The XPS developer: XPS has no bone limit per mesh.

Random XPS user: when importing the model in max or blender, it is split into many pieces
The XPS developer: XPS do not split a mesh into many pieces. the max exporter by mariokart64n do split meshes.

Random XPS user: I export the model (from 3ds max) in .mesh.ascii format, that happens.
The XPS developer: That's what I said. XPS does not split meshes. The 3ds max exporter by mariokart64n is the cause of your problem.
The max exporter developer: yeah there was a limit so there was a auto splitter. Essentially under options there’s a bone limit count or something that you can increase to 999999999 from 50.. or something

These statements sound contradictory, But you can believe the developer. They know what they have done themselves. And you've gotten the hint, on how you can fix your problem in 3ds max.


Some (true) facts:

1) The view of the models that you see in a 3D editor like Max or Blender is not always what the models really are.
For example, the same models in the same 3D editor, with different settings of the 3D editor:


Is the surface of the model now smooth like skin, or edgy like a diamond? How can you know it?

2) Here's the proof that XPS does not split meshes:
DOWNLOAD link of all data(s): https://www.sendspace.com/file/991roq
2a) The model is exported from Blender as FBX format. It has one mesh. This mesh is is influenced by 235 bones per mesh
2b) The FBX format is converted to "in.mesh.ascii" with Noesis and this script http://xnalara.org/viewtopic.php?f=17&t=1139
2c) The "in.mesh.ascii" is loaded in XPS 11.8.8 using "Modify-->Load GenericItem ..."
2d) The model is converted in XPS 11.8.8 as "in.mesh", using "Modify-->Save GenericItem" with default settings.
2e) The "in.mesh" is loaded in XPS 11.8.8
2f) Using the XPS "Material Editor", the mesh name is changed from "mesh01" to "head". Normal map and Specualr map added. RG is modified from 5 to 40 to 41. Render Paramter changed from "0.1" to "0.15" ...
2g) The model is exported as "out.mesh.ascii", using "Modify-->Save GenericItem" with default settings.
2h) The model is imported in Blender 2.49, using this importer script version 1.8 https://xnalara.forumotion.com/t18-gemeshasciitobin-addcameratargets-modpublisher-changebonenames-meshbintouvmap-changescenefile-modprotector-mesh_cleanup-and-autotexture-utility-s
2i) The result is:

==> 235 bones per mesh
==> nothing splitted

If you make the same effort and present your problem in the same way, then I can show you where your mistake is.

chao

My heart is full of joy that a new version of XPS was released. Thank you so much XNAaraL. The new updates, especially better memory management and pose/scene previews are going to be very useful.

I cannot wait for new versions.

LORD MJ wrote:My heart is full of joy that a new version of XPS was released. Thank you so much XNAaraL. The new updates, especially better memory management and pose/scene previews are going to be very useful.

I cannot wait for new versions.

Thanks a lot.
So you give this version the LORD MJ's Seal of Approval?

Which features do you want for the next version?

XNAaraL wrote:
Thanks a lot.
So you give this version the LORD MJ's Seal of Approval?

Which features do you want for the next version?

You are welcome.

Every version of XPS gets my Seal of Approval. It is such a wonderful program enabling us to create amazing things.

I don't have anything in mind for future versions. I've been using XPS for a few years now, but in a casual way because I can never find the time to really dig into the program and realize some of the many ideas I have in mind.
Every version of XPS brings a pleasant surprise in the form of new interesting features. I'm a casual user right now, but when I get serious, I know I will make use of all the new features that get added with each new XPS version.

Hi,

Any may build?

uyesuyes wrote:Hello again,

I deserve what you say. Unfortunately, it is impossible to deal with the programs sold to such high amounts. Now I'm trying to learn how to use the blender program.

However, I hope to share new versions occasionally.

I wish you a good day.

uyesuyes wrote:Hi,

Any may build?

The Blender 2.80 release is planned to be ready in July.
The Blender 2.89 release plan is there https://code.blender.org/2019/04/2-80-release-plan/
There was already 2 Blender Developer meetings in May (13 May 2019 and 6 May 2019).
Next Blender Developer online meeting is on Monday, 20 May 10:00 CEST / 8:00 UTC. It will be on #blender-coders on blender.chat.

For XPS 11.8.9 (the 189th XNALara/XPS release), nothing is planned at the moment.

User Feedback and Requests
XPS has maybe magnitudes of more users than people who are involved with making it (It is just me myself). That makes handling user feedback and feature requests normaly nearly impossible.

Therfore I had try to organize myselves in ways that development and users can cooperate closely. You can find this information listed on Deviantart. Feel welcome to use this journal and get involved with making XPS better.

Suggestion thread: https://www.deviantart.com/xnalaraitalia/journal/Vi-domando-un-parere-XPS-LAB-333144557
Bug Report thread: https://www.deviantart.com/xnalaraitalia/journal/Bug-Reports-on-any-XPS-version-615273344

It doesn't really matter whether your "idea request" it's already there, already planned, a great new idea, or simply not possible.

At the moment nobody seems to have a new idea which should be implemented additionally.

Furthermore, since 4 years here is not even posted a single image, made with XPS, in our forum. XNALara pictures Feel welcome to change this lack of interest

Just asking but in future updates do you plan on improving XPS shadows?
There is nothing wrong but defaultly XPS not taking the shadow of transparency material correctly
I mean I ve created a square mesh and applied a lenflare on it but the shadow taking a black square, not the lenflare and it alpha.
Both default shadow and advanced shadow have the same problem like that.
Just ask if possible

ngovandang1997 wrote:Just asking but in future updates do you plan on improving XPS shadows?
There is nothing wrong but defaultly XPS not taking the shadow of transparency material correctly
I mean I ve created a square mesh and applied a lenflare on it but the shadow taking a black square, not the lenflare and it alpha.
Both default shadow and advanced shadow have the same problem like that.
Just ask if possible

Just saying,
read more: https://developer.nvidia.com/sites/all/modules/custom/gpugems/books/GPUGems/gpugems_ch12.html

Nvidia GPU Gems by Philipp S. Gerasimov wrote:Rendering to depth-only is very fast (many GeForce FX GPUs have double-speed "depth-only" rendering features), so it requires minimal overhead, even in low-overdraw situations. Transparent objects are not rendered in the depth-only pass, because transparent objects do not update the depth buffer

I hope thats helps. If not, then read more https://en.wikipedia.org/wiki/Shadow_mapping

wikipedia wrote:this transformation is applied at the vertex level, and the generated value is interpolated between other vertices

Now this causes an issue with shadow mapping because with the current depth shader it only have access to the quad geometry and have not access to the transparency texture.

Told you!
I am not Joking.
End

Not joking:

 can't you just forget the old shitty happens? Do you think that I forgot who you are and what happened?
I am still talking because I love this but I start thinking this becoming shit not because of people but right because of the creator.
 When will you stop acting like a kid and start grow up huh? Your mom didnt tell you is drama is not good, huh? Or even your mom is the queen of drama? What a shitty mom to teach her childs.
What? How do you feel after I tell you that? Is that cool? Thats exactly what are you doing to me, bastard. Your bitchly mom was fucking a dog infront of your dad's dead body and impregnant before she born you, ask her is that true? What are you aiming for by mention the old shit happens?

People now come to XNAlara just because there is most porters are porting models from game now aday, they dont need your program or formats to do their renders.
 5 years all the time I just want its improved just abit, do you see that I still working after your block on DA? Thats time I was a noobs but I already known your were one of the creators and developers of XNAlara Studio, but right now after 3 years you are still acting like a kid likes 3 years ago?
Can I ask how old are you?
Being bastard is that cool, huh?

well, this is the reason for this people are leaving.
Anyway, feel free to delete this or do some replies to me, motherfucker. Or if you are a man then keeps this and lets people read how bastard you are, kid!
I should not talk to you before even 3 years ago. Thats my mistake for talking to you who was born by a bitchly mom and a dead dog.

You have no right to insult people!

Get lost!

Nice to meet you. I have been using XPS since this year.
When I knew this software, I was very happy that the update was made recently because there was no update for a long time.

I am not familiar with the history of the community, but I am sad that few people are concerned about software advancement and withdrawal.

This software is mostly used for porting existing games, but it may have many other uses as well.
Many 3D softwares, especially those with animations, are tight on HDDs and too heavy. However, XPS does not have those drawbacks.
It is portable and very light file size and good performance.

What I consider a drawback with this software is that the alpha channel is not output cleanly during PNG export. There is a fringe.

XNAaraL, what specifically do you want? Your software is not only a port tool. It has excellent properties as a 3D viewer.
I am not rich. So, continuous support is difficult but it is possible to donate for sometimes. Your work is worth it.