We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

3D Model is missing when converting PPTX to PDF after upgrading Aspose.Slides

Hi,
I just upgraded my aspose java products to latest version (21.8).
After the upgrade a pptx with animation doesnt get converted (blank page).
When I used version 19.2 it did get generate well.
Adding how it was generated in 19.2 + how it generate in 21.8 (aspsoe-slides).

After a small research I noticed that it stop working well between version 20.10 to 20.11 of aspose slides.

I coudnt upload the source file because its too big. (Only animation inside the pptx)
I uploaded the two outcomes of the pdf.
Examples.zip (1.4 MB)

@operationsdotbcs,
Thank you for posting the query. Unfortunately, I cannot investigate this case without your PPTX file. Please try to create a presentation sample or share a link to the file in some file storage. Also, please share the code example reproducing the problem.

Hi,
please try this link:

Code:
String dataDir = Utils.getDataDir();
String[] fontsList = new String[8];
fontsList[0] = (dataDir + “/usr/share/wine/fonts/symbol.ttf”);
fontsList[1] = (dataDir + “/usr/share/fonts/msttcore/arialbi.ttf”);
fontsList[2] = (dataDir + “/usr/share/fonts/msttcore/calibri.ttf”);
fontsList[3] = (dataDir + “/usr/share/fonts/msttcore/ariali.ttf”);
fontsList[4] = ("/home/ec2-user/usr/share/wine/fonts/symbol.ttf");
fontsList[5] = ("/usr/share/wine/fonts/ttf/wingdings/wingding.ttf");
fontsList[6] = ("…/usr/share/wine/fonts/ttf/wingdings/wingding.ttf");
fontsList[7] = (dataDir + “/usr/share/wine/fonts/ttf/wingdings/wingding.ttf”);

	FontsLoader.loadExternalFonts(fontsList);
	Presentation pres = new Presentation(dataDir + fileId + "." + extension);
	dataDir = dataDir + fileId.split("\\.")[0] + ".pdf";
	pres.save(dataDir, SaveFormat.Pdf);

@operationsdotbcs,
Thank you for the presentation file and code example. I reproduced the problem with the missing 3D model when converting it to PDF. I logged the issue with ID SLIDESJAVA-38622 in our tracking system. Our development team will investigate this case. You will be notified when this problem is fixed.